By Peter Bell

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.

Comments
Our DBAs have triggers setup that will flush the cache when changes are made to the data. So, the XML is always in sync.
# Posted By Andrew Powell | 10/31/06 12:27 PM
That would do the job nicely! Unfortunately I don't have a dba or I'd do the same :->

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.
# Posted By Peter Bell | 10/31/06 5:28 PM
BlogCFC was created by Raymond Camden. This blog is running version 5.005.