Hi Eddie, I often use the User to hold this kind of information, like their country, their language preferences, etc.. This doesn't mean you should set it as an attribute (as this would be saved into the session), but if you give your user a class variable to hold this i18n object, you can set it via filter and retrieve it from everywhere later.
Sure there's other ways to do this (store it in request or response for example), but I like to use the user. Hope this helps. Daniel On Jun 20, 5:33 am, EddieG <[EMAIL PROTECTED]> wrote: > Hello everybody, > > could you please give me a hint, what might be the best way to make > data from a filter class global? There are various possibilities, but > I don't have the slightest idea which is the best... > > In my case, the filter gets an I18n-Info-Object from the database. And > it directly sets the user culture. But I will need the I18n object > itself for more than that later and don't want to retrieve it anew > each time. So that object should be globally accessible! > > Thank you very much, > Eddie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
