Hi, As I see it I would love to be able to use symfony2 components out of the box in a non symfony application with minimal fuss, that is I do not wish to go and implement a database abstraction just to use the security layer. So I entirely understand shipping default implementations that have dependencies like doctrine. But I do like separation of concerns and would love to use the security component with my json cobol dropfile interface data access layer (for example) without having to basically reimplement the whole thing (think sfGuard and sfDoctrineGuard) so a well defined interface is needed.
Although we implement support for certain dependencies ourselves, there is (and must be) a clear interface that allows to replace it by custom implementations. Ahh well thats settled for me then. As long as I have a way of selecting my implementation of the interface, and the interface is generic enough, and when I configure it to use my implementation the other implementation can be safely deleted (or ignored and does not get parsed each request). It seems the main arguments left then are size on disk of the components? or have I missed the whole point. Thanks Dave -- 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
