On 10/31/14, 1:52 PM, Sherif Ramadan wrote:
So for the purposes of this discussion and in an effort to remain on-topic
and productive, let's keep all of the FIG/PSR and other third party efforts
out of the discussion unless it is intended to improve/help this particular
RFC. Please keep in mind that this is a PHP internals discussion and not a
FIG/PSR discussion. This RFC is about core PHP and I really don't care how
many competing ideas exist out there that are closely or mildly related to
this RFC.

Discussing prior-art for a proposal is entirely on topic. We do it all the time when comparing PHP to other languages and their syntax, for example. Internals should be informed by user-space usage patterns.

This RFC has two primary goals in mind:

1) Expose the parsing/handling of the HTTP request to userland in a
consistent way

It already is. It's the access TO that parsed data that is currently clunky. That's a problem worth addressing.

2) Avoid having the request parsed/mangled at multiple levels during the
request by presenting one central place to handle the parsing

This only applies to the body of a request; other properties have well-defined and not really variable parsing rules called HTTP.

A better way to parse the body is useful, and we've been discussing that in FIG. Please look at the existing discussions and prior art before continuing. That's also a much smaller, tighter discussion than request/response interfaces.

These goals can not be achieved purely in userland, because you would
potentially have to do the parsing step twice. I wish to make it possible
for the user to override that with their own implementation just like they
can override the Session handler with the Session interface.

How we end up deciding to do that may change from my initial proposal, and
that's fine, but let's focus on that rather than getting off topic about
other third party efforts.

Thanks!

Those 3rd party efforts are entirely on topic. That's the point.

--Larry Garfield

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to