On 07/26/2012 01:05 AM, Fabien Potencier wrote:
I started work on extracting Bundle from HttpKernel into a Bundle
Component <https://github.com/symfony/symfony/pull/4819> with the
goal of promoting reusability of Bundles as a
packaging mechanism outside the scope of HttpKernel applications. My
main reason for extracting Bundle was because I didn’t want to
depend on an “HTTP Kernel” in my non-HTTP application.
On Thursday, July 12, 2012 8:06:23 AM UTC-7, Beau Simensen wrote:
HttpKernel is indeed a component with many different facets. Frankly,
I've never envisioned a need for the bundle system outside Symfony,
the full-stack framework, and I'm not sure people will actually use it
that way. Do you have any idea in mind for reusing the bundle system?
I mean, if there is not a strong demand, is it worth the effort (even
if conceptually, it totally makes sense)?
Drupal is using both Kernel and bundles (or will as soon as another
patch lands), but not using the full stack framework. For us, Bundles
was just the most convenient way to allow Drupal extensions (modules) to
tie into the DI container.
I also agree with splitting HttpKernel into HttpKernel and AppKernel or
something. There's a lot in HttpKernel that has nothing to do with HTTP
at all. That may not have been the original intent, but that's how it
ended up working. That actually confused us for a while between
HttpKernel and Kernel, because they were in the same component.
--Larry Garfield
--
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
