Implementing the interface does not seem to be the problem. Identifying which part of Symfony caches what and where surely is. Otherwise, there's nothing to replace.
On Mon, May 28, 2012 at 4:17 PM, Eriksen Costa <[email protected]>wrote: > There was a PSR proposal for a caching interface. But then the coding > standards PSR proposal gather much more attention and since then anyone > talked about the caching interface. > > The last one I read was a good proposal but it did not got much attention: > https://github.com/tedivm/fig-standards/blob/Cache/proposed/PSR-Cache.md > > Getting the cache PSR a priority again would help to let the caching > consistent in Symfony. > > > Eriksen > > -- > Blog: http://blog.eriksen.com.br > Twitter: @eriksencosta > > > On Mon, May 28, 2012 at 4:04 PM, Klaus Silveira > <[email protected]>wrote: > >> So, the app/cache folder is full of various caches from different parts >> of the Symfony ecosystem. There are Twig, Doctrine and Assetic caches, as >> well core framework caches (routing, class map, etc). Recently, i've been >> trying to store such caches outside the filesystem, being more specific, >> Memcache. >> >> I've already had some success with Twig and Doctrine, but i'm curious >> about the other parts that populate the cache. It's quite difficult since >> there isn't a common caching interface, being each caching functionality >> independent. Did anyone managed to change the way the router, class map and >> other Symfony features cache? >> >> I'm trying to gather as much information as possible in order to build a >> single caching interface, allowing you to easily change between caching >> endpoints: Filesystem, Memcache, Database, S3, etc. >> >> -- >> 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 > > -- > 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 > -- Klaus Silveira (011) 8564-2492 www.klaussilveira.com -- 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
