I've found static publishing to a .html file to be a real boon insofar as resources are concerned. Cuts CF and the db clean out of the picture, although as has been said this does nothing for disk i/o. This can create problems, though, if you need to keep users' sessions alive, since they are not hitting .cfm pages anymore. I more or less bandaged this over by publishing to static .cfm pages. i.e. totally static .html content still, but with the .cfm extension to keep CF in the picture at least a little. Solved the problem but I was never happy with doing it.
The real bear is creating a seamless publishing mechanism so non-tech users don't know they are creating static content in the first place. Once thats done its pretty smooth sailing. -- --mattRobertson-- Janitor, MSB Web Systems mysecretbase.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:196373 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
