Re: [xml] Output from libxslt
- From: Daniel Veillard <veillard redhat com>
- To: Matt Sergeant <matt sergeant org>
- Cc: "xml gnome org" <xml gnome org>
- Subject: Re: [xml] Output from libxslt
- Date: Sun, 11 Mar 2001 05:58:39 -0500
On Sun, Mar 11, 2001 at 10:28:24AM +0000, Matt Sergeant wrote:
I can get libxslt to output using the right output method to a file, no
problem. It's just xsltSaveResultToFile. But I want to be able to output
to memory, or with callbacks...
Unfortunately there's no example of xmlOutputBuffer anywhere in the code,
which looks like how I would do it. So my question before I just start
hacking, is what is the "ioctxt" void pointer? Is it somewhere I can stash
a private structure for use in the callback? Or will it get overwritten?
If so, the output callbacks really need some way of storing a private
pointer, otherwise it's going to be impossible to make some of this stuff
thread safe.
Okay, an IO output bufffer can be user defined to output to memory,
a protocol stack, a database ...
It's like a device handler in most OSes, there is a set of entry points
(i.e. the write and close callbacks) and a context pointer which is
user definable.
Yes the ioctx argument is the context defined by the user and passed
as the first argument of the write and close callbacks.
More informations can be found in:
http://xmlsoft.org/xmlio.html
http://xmlsoft.org/html/libxml-xmlio.html#XMLOUTPUTBUFFERCREATEIO
Seems I need better descriptions of the functions arguments or usage
description, feedback welcome :-)
Daniel
--
Daniel Veillard | Red Hat Network http://redhat.com/products/network/
veillard redhat com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]