Re: [xml] register i/o callback functionality

[Daniel Veillard <veillard redhat com>]

On Fri, May 28, 2004 at 11:58:51AM -0400, Rob Richards wrote:
> From: Daniel Veillard
>
> >   Now if you come with a realistic example of why you would need per
> > context registration that might be added. One thing that won't work
> reliably
> > is to dynamically register and unregister new I/O handlers. It's better
> > to register once global entry points and handle potential thread
> contention
> > down in the routines, as the registration/unregistration I/O API are not
> > thread safe.
>
> In this case, all default handlers are overriden. file, http and ftp. This
> was done so that the security mechanisms could be handled. (i.e. checking
> wether remote file access is allowed, what directories are allowed to be
> access, etc...).
> I figured that was the case but wanted to make sure before going down the
> rat hole, so trying to see if there is anything that can be done in our
> matchcallback routines.

Since the input is "just" the URI string, and that string may come from
within the document it seems only an API addition is possible, this is
not gonna be easy to design,

Daniel

-- 
Daniel Veillard      | Red Hat Desktop team http://redhat.com/
veillard redhat com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/