[Flow] Re: HTTP Reverse Proxy and "HTTP components"

[Christopher Hlubek]

Well we have some foundation but honestly for me it still doesn't feel right. The main problem is the high coupling inside Flow which doesn't allow us to split it into separate packages for now and leads to a suboptimal architecture.

I do some research right now to see if we can find a backwards-compatible way to allow for much greater flexibility in terms of handling HTTP requests. I have the feeling that we can open up the framework substantially by this and achieve much looser coupling which can lead us to individual packages for Flow. We can also have the absolutely same MVC-architecture on top so I see no need for user-facing changes there.

I pushed a first rough prototype here https://github.com/chlu/TYPO3.Flow/tree/http-component and will work on making the Router independent of MVC so it will route to HTTP components which are much more lightweight to handle requests and do custom stuff. Also I think we really need some kind of middleware approach. As always AOP is only suitable for unplanned extensibility and cross-cutting concerns and doesn't apply well to handling HTTP requests in a flexible way (IMHO).