Re: [xml] register i/o callback functionality

[Mike Hommey <mh glandium org>]

Rob Richards wrote:
> Note that I am no apache expert, so just summing up some of the things I
> have seen while working with libxml under apache.
>
> Those calls are safe to call multiple times. One reason PHP 5 uses 2.5.10 as
> its minimum version is that at least in 2.5.8, there was a problem calling
> CleanupParser multiple times. When the xml extensions were being developed
> each one was calling the init/cleanup, which is where the issue in 2.5.8 was
> hit (though has since been changed to a single library call so that its
> called only once). I assume that on a reload, any module would be resetting
> its state in any case, so they would be expecting the parser to be getting
> initialized (which they would either do explicitly or libxml will do it when
> needed).
>
> > From what was found, pretty much no other intitalization of libxml should be
> done in the module initialization. For example, the generic error handling
> functionality had to be isolated by moving it into the request startup
> rather than module startup as it was bleeding into other modules and causing
> them problems - like crashing apache :). Since then, other than the recent
> i/o callback issue, there havent been any reported problems with other
> modules

One other issue I thought about is all the global variables. It is not 
really a problem with apache 1.3 (provided that modules don't set them 
in their initialization, but rather in the request loop), but definitely 
might be with apache 2.0 with the threaded "engine".

Mike