Hi everybody,

I'm currently developing and planning some pure Command Line tools which all rely on some Symfony components. After some days of developing I noticed that it would be nice, if I were able to use the bundle system,because then I would be both able to reuse some code and structure the app's code in a clean way. My only problem is, that using the the Symfony Bundle structure would require two problematic new components: HttpKernel and HttpFoundation.

While I maybe could accept that I have to add a dependency to the HttpKernel Component, adding the HttpFoundation to the project seems far away from a good compliance with the SoC principle. So I wondered how to use the Bundle system, and other goods provided by the Kernel, in apps which aren't related to HTTP in any way, but I found no way to do this without changing code in the HttpKernel component without requiring such unused dependencies as the HttpFoundation component (if there is a way to do so, I'm sorry for posting my question to the dev-mailinglist).

So I took a look at the HttpKernel code and the following possibilities came to my mind: * Make the KernelInterface and Kernel class standalone and let the HttpKernel extend the Kernel while implementing the HttpKernelInterface * Make the KernelInterface and Kernel class standalone and leave the HttpKernel untouched but introduce a "Fat" HttpKernel (No Idea how to name it^^) which does extend the Kernel class and adds the handle method of the current Kernel class * Seperating the Kernel class and interface + all classes which are not related to the HttpKernel in a new Kernel component (the Kernel Component has to be refractored e.g. as described above), and make the HttpKernel component the component for all the HTTP related stuff which depends on the new Kernel component and on the HttpFoundation * Moving the Module system to its own component (completely independent from the above ideas)

Don't know if any of these ideas is even possible, but if you think that one of this idea could be realized (and has chances to be merged) I could write a first draft and open a PR so implementation details could be discussed there.

cheers,

drak3


--
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 symfony-devs@googlegroups.com
To unsubscribe from this group, send email to
symfony-devs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en

Reply via email to