@Matt, having pattern and wildcard cannot work since most cache providers to not expose API for this type of usage. =(
I personally think Doctrine Cache is good enough as a start, but of course there're updates that we could do. If FIG would want to provide a common interface or even a common code for everyone to use it, I'd love to give a hand implementing it. Personally I feel extremely tired nowadays of current threads rolling out there as people are discussing (sorry, but..( stupid personal preferences instead of common goal. Cheers, On Sat, Mar 23, 2013 at 3:03 PM, Matt Robinson <[email protected]> wrote: > I'd love to see FIG standardise a cache interface and for Symfony to have > an exemplary implementation of it, but that doesn't necessarily mean it > needs to be a Symfony component if something better already exists. > > Personally though I don't think Doctrine Cache is that something. At least > not yet. It doesn't quite feel "Symfonic" (weird, since it's already part > of Doctrine ORM), and since its current interface has no methods in common > with the PSR proposal, it seems it would be more work to change it (and > everything that uses it) than to accept one of the PRs mentioned below and > document it. I could be dead wrong though; DC's support for patterns & > wildcards is really neat, for example, and it's a stable and well-tested > library as far as I can tell. > > On balance, I think I'd rather see a new Symfony Cache component. > > On 23 Mar 2013, at 17:21, Florin Patan <[email protected]> wrote: > > Hi Fabien, > > > Nice to see some activity for this. > > I think we should get this done after FIG does their job as it would help > the > community but after a long time discussing this, FIG has been quiet this > week. > > Maybe a fresh set of eyes from Symfony community members on the > FIG ML here: https://groups.google.com/forum/#!topic/php-fig/UkSWS48eEgo > > Paul did a great job in trying to summarize and get the best out of all > proposals for FIG and there's also the long standing proposal from Robert. > > As for Symfony2 strictly, if FIG adopts a PSR and then Doctrine makes > a move to become compatible with it I don't see why we couldn't rely on > Doctrine Cache to provide the caching layer, just like we have Monolog. > > Have a nice weekend. > > > Best regards, > Florin > > On Saturday, March 23, 2013 7:11:56 PM UTC+2, Fabien Potencier wrote: >> >> Hi all, >> >> There is probably one missing component in Symfony: a cache one. There >> is already a ticket and 4 PRs on this topic, but I think we need to >> discuss what we want to do before writing any code. Also because there >> have been a lot of discussions already on the FIG group, so we also need >> to discuss what is our position about this too. >> >> I'm pretty sure that we won't have time to finish anything serious >> before 2.3, so we have time to get it right. >> >> For reference, here are the ticket on Symfony: >> >> https://github.com/symfony/symfony/issues/1513 >> >> And the 4 PRs: >> >> https://github.com/symfony/symfony/issues/3211 >> https://github.com/symfony/symfony/issues/3225 >> https://github.com/symfony/symfony/issues/5902 >> https://github.com/symfony/symfony/issues/5903 >> >> Let's start the discussion! >> >> Fabien >> >> -- >> Fabien Potencier >> SensioLabs CEO - Symfony lead developer >> sensiolabs.com | symfony.com | fabien.potencier.org >> +33 1 40 99 80 80 >> > > -- > -- > If you want to report a vulnerability issue on Symfony, please read the > procedure on http://symfony.com/security > > 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 > --- > You received this message because you are subscribed to the Google Groups > "Symfony developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- > -- > If you want to report a vulnerability issue on Symfony, please read the > procedure on http://symfony.com/security > > 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 > --- > You received this message because you are subscribed to the Google Groups > "Symfony developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Guilherme Blanco MSN: [email protected] GTalk: guilhermeblanco Toronto - ON/Canada -- -- If you want to report a vulnerability issue on Symfony, please read the procedure on http://symfony.com/security 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 --- You received this message because you are subscribed to the Google Groups "Symfony developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
