Hi Fabien, Thanks for the feedback! I'll wait for information on the RFC process. I answered a couple of your questions below.
On Wednesday, July 25, 2012 11:05:09 PM UTC-7, Fabien Potencier wrote: > 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 think the concept of "*an environment made of bundles*" is something that can easily extend beyond the full-stack Symfony framework but I can see why maybe that wasn't a high priority in the beginning. I am actively building a command line application that has a plugin/bundle concept that closely matches Symfony's bundles. Rob took a look and decided to try and make my system work with Bundles based off of Symfony's BundleInterface so that certain classes of bundles could be dropped into my app as-is and reuse at least some of its functionality. The idea of standardizing on a plugin/bundle structure was a nice one and this is what initially led me to try and extract Bundle from HttpKernel. I quickly realized that standardizing on the Bundle part was indeed nice but it meant a lot of work on the application side to consume and use Bundles. Work that was already being done by Kernel. I mean, if there is not a strong demand, is it worth the effort (even > if conceptually, it totally makes sense)? I really have no idea how strong the demand is for this and the effort could be considerable. :) So it very well may not actually be worth the effort. At this point I'm prepared to use the existing Kernel but would be motivated to eventually work on moving in the direction of not depending on HTTP Kernel or HTTP Foundation at some point in the future. So, Kernel does almost everything you want, but still, you don't want > to use it, is that correct? Kernel actually does everything I want. The problem is the implication that it has anything to do with serving HTTP at all. That implication is enough to give me pause and consider whether or not I'd use a powerful and existing Symfony component or find another way to do it. Given this choice awhile back I chose to roll my own (patterned heavily after Composer). Had I seen a Kernel component with some examples of how to create a standalone non-HTTP serving application using it I might have more seriously considered looking into that instead. I cannot guarantuee that your final proposal will be merged, so first, we > need to discuss the changes as an RFC. A guarantee on merge is hard to give, but I would imagine that the likelihood that something *won't* be merged is sometimes easier to guess. ;) I was mainly looking to see whether or not that might be the case here. In any event, I think the RFC process will help a lot. -- 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
