On Wed, Mar 21, 2007 at 02:45:36PM -0400, joel reed wrote:
> I think I'll rename this thing curlIO.{h,c}. Any thoughts on
makes sense.
> configuration API? I think I need to change xmlIO to call a
> configuration callback function or some such thing, as my current
> xmlIOHTTPSSetup approach is library wide, but what we really want is a
> context specific configuration capability. Also, I'm not sure it makes
should we need to compile in nano* if curl support is configured in ?
I would probably change xmlRegisterDefaultInputCallbacks() and
xmlRegisterDefaultOutputCallbacks() undefining LIBXML_HTTP_ENABLED
and LIBXML_FTP_ENABLED and using a special register entry point for
curl. Some of the things which may not be trivial are the write
function for FTP and HTTP, at least testing they work okay.
> sense to wrap every possible curl configuration option
> (http://curl.haxx.se/libcurl/c/curl_easy_setopt.html). I'm thinking if
> there was a callback that got the context pointer, maybe all we need is
> a function which returns the CURL*, then the application could use
> whatever CURL config options were available. There are a ton of curl
> config options. Does this sound OK?
You mean the (void *) context used as first arg for read/write/close,
then yes sure, that is curl specific and I would assume it's a
CURL *handle, but it could be libxml2 specific structure with the handle
and provide an accessor.
I'm sure other people have used curl in a libxml2 context, their feedback
would be welcome.
Daniel
--
Red Hat Virtualization group http://redhat.com/virtualization/
Daniel Veillard | virtualization library http://libvirt.org/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
_______________________________________________
xml mailing list, project page http://xmlsoft.org/
[email protected]
http://mail.gnome.org/mailman/listinfo/xml
