Hi Andrei,
On 3/5/07, Andrei Zmievski <[EMAIL PROTECTED]> wrote:
Pierre,
How's it going with this list you posted? Last I heard you had some
issues with ext/session. Can you elaborate please?
The issue is not specifically with the ext/session but with extensions
accessing the input data during RINIT. For example, ext/session tries
to access the HTTP input to fetch a possible SESSID.
To keep the JIT at runtime only I like to add an internals API to
access the input value as raw/binary data, without decoding them. It
will be the responsibility of the extension to correctly decode the
data.
It would be possible to implement JIT in each extension, but as soon
as the script uses a different encoding than the extension (which is
defined by http.input_encoding or another specific php.ini option), we
will have to decode the complete input two times (or more on error).
I'm reviewing the other extension for the http_globals usage. I will
come with the API and the patch as soon as possible.
Cheers,
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
