On Dec 15, 2011, at 13:38 , Alexandre Salomé wrote: > Hello, > > I recently worked on translation system, and I had some tricky needs > (translations are stored in database, cached in Redis and each domain/locale > should have a Redis key with the last update of catalog). > > Currently, the implementation is very raw (option cache_dir) and suffer > from lot of limitations: > • Not warmed > • Clear cache to update translations > • And so on > I would like to develop this part to add some warming/cache mechanism, > powerful enough to support the case I have (even if I need to adapt it to my > work). > > We could also take benefit from resource watching to detect catalog updates > with file systems. Well it's a big topic in translations and I would like to > have your advice about it. > > Should probably be discussed during a IRC meeting, but first, let's discuss > of it here.
I havent done much with the translation layer myself and in the few places where I did it was very limited. But sounds like this is indeed an important topic to address. Just FYI for the cache layer there is a PR that might be relevant for cache clearing: https://github.com/symfony/symfony/pull/2857 regards, Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
