> > >>You can manually cache these variables in the application scope, but I >>was looking for something more specific. An example of such data might >>be: a default sort order, l10n texts etc. >> >> > >since you mentioned locales, the wheels will fly off in an environment where >locales are user (session) based. > But then you can load a struct with a struct of translations for every laguage available and a default language. And you could save the userlanguage in either hist ClientPageContext or SessionPageContext (depending on the fact if it's a known or a guest user).
>>So this would work like a normal client or session variable, but these >>variables would be unique for each page (haven't though about includes >> >> >coming from an i18n world i would argue for unique user/pages. or am i >misunderstanding your intent? > I think I don't understand what you don't understand :) >>keywords etc. One could store these in the clientscope or the session >>scope, but then these would be accessible from any other page aswell. So >>in this case there would be a pageSession and a pageClient scope to >>handle these kinds of data. >> >> >ah yes. makes sense. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
