+1 from me on the ArrayAccess interface - that makes it so easy to use! On Monday, March 25, 2013 3:08:17 AM UTC+13, Kinn Coelho Julião wrote: > > I believe we can simplify rather than complicate. > Once the FIG decide something related to interface, and developers > implement the interface, SF2 can use any caching layer since the interface > will be standard. > One solution that I like and is very simple, is to implement the > ArrayAccess as in the example below: > https://github.com/PHPFluent/Cache/blob/master/src/PHPFluent/Cache/Cache.php//With > the interface, it will be not just doctrine, but > "FIGCacheInterfaceSomething" > > It is so simplistic, that it may fail in the future... anyway, people can > extend it to create it owns > > I would love to have something like this in Symfony: > > $cache = new Cache; > $userList cache = $['userList']; > / / > ... > $cache = new Cache; > $room = $cache["chatRoom_ {$ parameter}"]; > > As you can see, it is simple and useful... everybody knows array(or must > know, what is PHP without array?)... You don't need to learn a new API for > this, it is a simples and pretty array that can take advantages of cool > enhancements done in PHP5.4 and PHP5.5 beta1 =] > > > > 2013/3/23 Amy Stephen <amyst...@gmail.com <javascript:>> > >> >> >> On Saturday, March 23, 2013 7:12:49 PM UTC-5, Guilherme Blanco wrote: >>> >>> >>> I am a huge evangelist of OS and I think PSR should release their own >>> code that everyone would reuse. I can't see better argument to probably >>> have same implementation being ported to PHP itself. But for now, I think >>> we have in FIG brililant minds that could help and their effort would also >>> help everyone. >>> >>> There is a FIG poll about this very question we are asked to use for >> providing feedback >> https://groups.google.com/d/msg/php-fig/3hPX9N0eru4/vnE3hHzqGkkJ >> >> Personally, I disagree with FIG releasing code as I prefer to see ways of >> leveraging project solutions between projects. >> >> However, either for or against, there is a place to share those opinions >> on the link above, but it's likely off topic to what Symfony decides is >> appropriate for the Symfony project. =) >> >> -- >> -- >> 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 symfon...@googlegroups.com<javascript:> >> To unsubscribe from this group, send email to >> symfony-devs...@googlegroups.com <javascript:> >> 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 symfony-devs...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > *---------------------------------------------------------* > * Kinn Coelho Julião* > * * > * kinncj.com.br > About.me/kinncj > * > *---------------------------------------------------------* >
-- -- 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 symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com 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 symfony-devs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
