Isaac, What's the benefit that CFMX offers in the Application scope?
Calvin <cf_snipalot /> > You'll be needlessly accessing the application scope anyway. The application > scope should really only be used for data which might change periodically > based on time of day, administrative interraction (i.e. "this feature is > currently unavailable due to maintenance"), or to refresh a cacheing > routine, etc. Data which is set, static and required on every page should be > set solely in the request scope, unless you're running CFMX and planning to > access it directly from the application scope -- which I prefer not to do > because imho there's no real benefit over using the request scope while > there are definite advantages to using the request scope if you end up > needing backward compatibility for CF 5. > > hth > > > s. isaac dealey 954-776-0046 > > new epoch http://www.turnkey.to > > lead architect, tapestry cms http://products.turnkey.to > > tapestry api is opensource http://www.turnkey.to/tapi > > certified advanced coldfusion 5 developer > http://www.macromedia.com/v1/handlers/index.cfm?ID=21816 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
