I stumbled over this while trying out 'pear package' which, while doing
xml parsing, re-assigns the variaous callback handlers depending
on the version during xml processing.
If this check causes problems, let me know.
This initial checkin has no changes to any of the libgd code so it can
be used as a basis for diffs. It also will not build currently because
of this. The PHP gd checks need to be incorporated along with a bit of
other config magic. It also shouldn't break the build and will only
take effect if you use --with-gd=php right now.
- append_child(): actually do an append child and not and add sibling
- what is called xmlDtd in libxml is actually the class DocumentType
in DOM. The domxml extension used a class DomDtd which is not defined
in the DOM standard. Instead of using DomDtd DomDocumentType is now
used. DomDtd has been renamed to Dtd but has not meaning anymore.
- added more functions
php.ini-recommended uses output buffer resulting delayed output during
"make test". User php.ini file is used anyway, since run-tests.php
invoke php for each test from there.
disappeared. It may be CVS doing this. I have put the nulls back, but we
may have to mark this as a binary file in th cvswrappers, or rewrite the
test to not output nulls.
filter chain instead of just down the rest of the chain. This fix will
speed up some unnecessary overhead introduced in the last patch.
Suggested by: Cliff Woolley <jwoolley@apache.org>
to do some trickery with the server_context to make sure it is always
valid within the current thread.
This patch makes sure the server_context is created in apache's
post_read_request hook phase, and then registeres a cleanup that
will NULL out the server context when the request goes out of scope.
Then, inside the output filters, if the server_context is null we
throw an error. Finally, instead of saving the output filter in
the server_context, now we store the entire request_rec pointer
in there.
POST bodies appear to be working now, although they are very inefficient.
The input filter is still just realloc()ing for whatever data comes
down the input pipe, and then sending this to PHP. This means that
we are doing some really nasty memory management on big POST bodies.
For now this it allows for unlimited input bodies, which means that
a big POST could potentially DoS a box by making it run out of memory.
We might want to put a limit on here just in case, at least until
we figure out how to consume input data more efficiently into php.
Apache 2 the input and output filter contexts are kept unique. We now
only depend on SG(server_context) for each request, and assume that
the same thread will process the entire request. At some point it
would be wise to separate the input and output contexts.
