I think this is what Benjamin and me was trying to explain the first time this topic was discussed.
I am not a big fan of the Bridge namespace as it will also include stuff that some people would not need (Zend Framework does this with Services) and embed the whole thing into the framework. This would not be an issue if the replacement of the sandbox / bootstrapper makes it possible to only specify what components etc you want to have included in a project (Gemfile). What is the difference in a Bundle and the Bridge namespace other that the name does not include Bundle and there would properly be some files in a bundle that does not have a direct link to the component clue code. I think that we are going to see two types of bundles. Application Bundles and Integration Bundles where the latter will only provide glue code to some 3rd party framework or component like Assetic and Application Bundles will be full of controllers and routes. Why is it that we cannot say Bundles may be used outside the Symfony2 Framework? And to end you have also yourself said that there would be no difference in a bundle and 3rd party code when it comes to sharing. "Everything is a bundle in Symfony2. Not only the code you write, but the core framework and third party code. It means that there is no difference between a code you write for your application and the code you want to share with others. At any point, you can share your code between projects" -- 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
