Admitted, the ACL system is different. It ships with implemented domain objects, not only with interfaces. This is possible since the ACL system is entirely self-contained, it's a closed system. Its entities have no relations to any of your domain objects, its entities also don't need to be extended to suit your needs, it just works out- of-the-box.
The component is usable standalone without Symfony. A developer can just take it, install all the dependencies and voilà he has a high- quality security solution. He doesn't have to dig into a bundle and extract provider classes. Also, if he decides not to use the ACL system, there is no dependency. The dependency is entirely optional. What exactly are the pros of moving part of the ACL system to the DoctrineBundle? Johannes On 1 Jan., 22:35, Henrik Bjornskov <[email protected]> wrote: > To use the whole ACL system you are currently required to use Doctrine DBAL > and Common. So why not move it to DoctrineBundle where thoose two things are > already a dependency? -- 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
