Generating Static XML with CF for Improving Performance
Andy Powell just posted a great article on using a file cache to persist datasets as static XML files rather than having to get CF respond to your spry requests. Only tweak I'd make would be an IsDirty or Publish mechanism which maps recordsets to changes in CF so whenever you updated the data through the app it would regenerate the appropriate XML files.





If anyone else comes on this link, the benefit of trigger based approach is that if multiple apps access the same db, you are sure to catch changes whereas an "in application" isDirty usually wouldn't catch changes by other apps or scheduled clean up SPs or whatever.