I don't really see really world exemple given interface we have actually but i think it's a thing to keep in mind for futur interface.
In my case i have a service who is doing both Authentification and User providing (i'am using a existing webservice who has all this method). So i have in this service supports and supportsClass method which is ugly for me because the method name give no concern about what object or class i support. I can always separe this service in two separated class and extends from another class to not rewrite some codes but it's a shame because interface are great for multiple implementations. -- 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 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
