Add support for Appserver-in-PHP, which could result in much faster executions.
Updated by Christopher Hlubek over 9 years ago
I played around with this and we have some problems with FLOW3 and AiP: sessions and Login don't seem to work, I was only able to login sometimes. RequestURI detection for resources is started at initialization, when AiP has no information about the RequestURI. We need to change that.
The routing sometimes generates URLs with a prefix of
/index.php/ which is annoying. I did not figure out yet, when that happens.
But there is one big design issue with the Request handling in FLOW3: we need to use the request handler (e.g. for SOAP requests or other flexible handling of requests) instead of building just web requests and the request handler doesn't expose any response object. So we don't get access to the generated content (could be fetched from output buffer) and to any headers that were set (I see no way to get these).
My idea would be to have a lowlevel and thin layer that could expose this information from the RequestHandler: each RequestHandler would have to use the environment to output information (like it does for getting arguments and headers), since we already have a special AiP environment in place and could collect data for each run.
Updated by Karsten Dambekalns over 8 years ago
- Status changed from Under Review to On Hold
- % Done changed from 80 to 0
- Has patch set to No
The changes have been abandoned, see https://review.typo3.org/#/q/topic:27322+status:abandoned,n,z