[Flow] RFC: Decouple request handling

[Jacob Floyd]

REST out of the box is a very important feature in my mind.

I did not understand the ideal solution you mentioned, but I can see how
passing around both request and response would be helpful.
Your short term solution sounds reasonable to me. Why does Request merge
everything right now? Would this change affect the ESI and caching work
that Robert has been working on?


On Apr 24, 2013 10:05 AM, "Bastian Waidelich" <bastian at typo3.org> wrote:

> Hello,
>
> as some of you might know I'm currently trying to improve out-of-the-box
> REST support in Flow.
>
> There is not so much missing code wise. But unfortunately we currently
> have a tight coupling though all different layers of a request (even though
> this has been greatly improved already by Robert).
> As a result even minor changes in the request API can lead to regressions
> easily.
>
> Therefore I'd greatly appreciate some feedback on:
> http://forge.typo3.org/issues/**45290#note-8<http://forge.typo3.org/issues/45290#note-8>
>
> --
> Bastian Waidelich
> --
> Core Developer Team
>
> TYPO3 .... inspiring people to share!
> Get involved: typo3.org
> ______________________________**_________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-**bin/mailman/listinfo/flow<http://lists.typo3.org/cgi-bin/mailman/listinfo/flow>
>