[Flow] [CORE] HTTP Reverse Proxy and "HTTP components"

[Robert Lemke]

Folks,

while reviewing a change set created by Alexander Berl [1] I learned
that he needs the proposed feature for implementing a reverse proxy for
Flow. At the same time, Christopher is touching a closely related topic
which he calls HTTP Components [2].

Then finally, as some of you might know, I've been preparing the
framework during the last year in order to implement a reverse proxy
myself. More specifically, I have created the HTTP foundation for it,
introduced the new bootstrap with sequence / steps and we prepared Fluid
to eventually support Edge Side Includes.

I feel like we (and me specifically) need to communicate more about the
plans and current parts we are working on, because once everyone has
finished their respective development, there will be the rude awakening
when we need to integrate the changes and agree on a common solution.

So, since I'm on it for quite some time now, I'd love to continue
leading the effort to create reverse proxy functionality in Flow.
There's a work package for Neos [3] which addresses this feature and I
plan to intensively work on it when I'm back (I'll be offline during the
next two weeks).

We can surely discuss making Flow more flexible and support various
things you might need in your own projects and implementations. But
let's refrain from ad-hoc solutions, especially now that we have a 2.0
release around the corner which won't allow us to introduce breaking
changes for the next year or so.

What are your need, plans, ideas for the HTTP request handling and a
reverse proxy?

Cheers,
Robert


[1] https://review.typo3.org/#/c/20028/
[2] https://github.com/chlu/TYPO3.Flow/tree/http-component
[3] http://forge.typo3.org/issues/45408

-- 
Robert Lemke
Lead Developer TYPO3 Neos and TYPO3 Flow
Co-Founder TYPO3 Association

Blog: robertlemke.com
Get involved: typo3.org – flow.typo3.org – neos.typo3.org