You might need to ensure that any cached data is persisted to a place where it can be recalled from when the application restarts. Or perhaps release a connection to "something" that you application maintains, and which you'd rather gracefully terminate rather than just let time out. Or maybe you do some logging on each request, but you just write to memory for performance reasons and the flush to the database en masse every X time, and you want to ensure there is nothing that hasn't been saved before you application shuts down.
Of particular interest is that onApplicationEnd is called anytime an application is terminated, whether it be a timeout, or if CF is shutting down. In the last example above, that's of great importance, because it's quite likely that you'll have stuff in memory that you don't want to lose when you shut down. I'm sure there's a million other neat things to use it for, but there's a sample few. cheers, barneyb On Sat, 12 Mar 2005 08:58:19 -0600, Andy Ousterhout <[EMAIL PROTECTED]> wrote: > Barney, > > What are some of the uses of onApplicationEnd? > > Andy -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:198567 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
