IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
</style><title>I/O Interfaces</title></head><bodybgcolor="#8b7765"text="#000000"link="#a06060"vlink="#000000"><tableborder="0"width="100%"cellpadding="5"cellspacing="0"align="center"><tr><tdwidth="120"><ahref="http://swpat.ffii.org/"><imgsrc="epatents.png"alt="Action against software patents"/></a></td><tdwidth="180"><ahref="http://www.gnome.org/"><imgsrc="gnome2.png"alt="Gnome2 Logo"/></a><ahref="http://www.w3.org/Status"><imgsrc="w3c.png"alt="W3C Logo"/></a><ahref="http://www.redhat.com/"><imgsrc="redhat.gif"alt="Red Hat Logo"/></a><divalign="left"><ahref="http://xmlsoft.org/"><imgsrc="Libxml2-Logo-180x168.gif"alt="Made with Libxml2 Logo"/></a></div></td><td><tableborder="0"width="90%"cellpadding="2"cellspacing="0"align="center"bgcolor="#000000"><tr><td><tablewidth="100%"border="0"cellspacing="1"cellpadding="3"bgcolor="#fffacd"><tr><tdalign="center"><h1>The XML C parser and toolkit of Gnome</h1><h2>I/O Interfaces</h2></td></tr></table></td></tr></table></td></tr></table><tableborder="0"cellpadding="4"cellspacing="0"width="100%"align="center"><tr><tdbgcolor="#8b7765"><tableborder="0"cellspacing="0"cellpadding="2"width="100%"><tr><tdvalign="top"width="200"bgcolor="#8b7765"><tableborder="0"cellspacing="0"cellpadding="1"width="100%"bgcolor="#000000"><tr><td><tablewidth="100%"border="0"cellspacing="1"cellpadding="3"><tr><tdcolspan="1"bgcolor="#eecfa1"align="center"><center><b>Developer Menu</b></center></td></tr><tr><tdbgcolor="#fffacd"><formaction="search.php"enctype="application/x-www-form-urlencoded"method="get"><inputname="query"type="text"size="20"value=""/><inputname="submit"type="submit"value="Search ..."/></form><ul><li><ahref="index.html"style="font-weight:bold">Main Menu</a></li><li><ahref="html/index.html"style="font-weight:bold">Reference Manual</a></li><li><ahref="examples/index.html"style="font-weight:bold">Code Examples</a></li><li><ahref="guidelines.html">XML Guidelines</a></li><li><ahref="tutorial/index.html">Tutorial</a></li><li><ahref="xmlreader.html">The Reader Interface</a></li><li><ahref="ChangeLog.html">ChangeLog</a></li><li><ahref="XSLT.html">XSLT</a></li><li><ahref="python.html">Python and bindings</a></li><li><ahref="architecture.html">libxml2 architecture</a></li><li><ahref="tree.html">The tree output</a></li><li><ahref="interface.html">The SAX interface</a></li><li><ahref="xmlmem.html">Memory Management</a></li><li><ahref="xmlio.html">I/O Interfaces</a></li><li><ahref="library.html">The parser interfaces</a></li><li><ahref="entities.html">Entities or no entities</a></li><li><ahref="namespaces.html">Namespaces</a></li><li><ahref="upgrade.html">Upgrading 1.x code</a></li><li><ahref="threads.html">Thread safety</a></li><li><ahref="DOM.html">DOM Principles</a></li><li><ahref="example.html">A real example</a></li><li><ahref="xml.html">flat page</a>, <ahref="site.xsl">stylesheet</a></li></ul></td></tr></table><tablewidth="100%"border="0"cellspacing="1"cellpadding="3"><tr><tdcolspan="1"bgcolor="#eecfa1"align="center"><center><b>API Indexes</b></center></td></tr><tr><tdbgcolor="#fffacd"><ul><li><ahref="APIchunk0.html">Alphabetic</a></li><li><ahref="APIconstructors.html">Constructors</a></li><li><ahref="APIfunctions.html">Functions/Types</a></li><li><ahref="APIfiles.html">Modules</a></li><li><ahref="APIsymbols.html">Symbols</a></li></ul></td></tr></table><tablewidth="100%"border="0"cellspacing="1"cellpadding="3"><tr><tdcolspan="1"bgcolor="#eecfa1"align="center"><center><b>Related links</b></center></td></tr><tr><tdbgcolor="#fffacd"><ul><li><ahref="http://mail.gnome.org/archives/xml/">Mail archive</a></li><li><ahref="http://xmlsoft.org/XSLT/">XSLT libxslt</a></li><li><ahref="http://phd.cs.unibo.it/gdome2/">DOM gdome2</a></li><li><ahref="http://www.aleksey.com/xmlsec/">XML-DSig xmlsec</a></li><li><ahref="ftp://xmlsoft.org/">FTP</a></li><li><ahref="http://www.zlatkovic.com/projects/libxml/">Windows binaries</a></li><li><ahref="http://opencsw.org/packages/libxml2">Solaris bi
the interfaces to the libxml2 I/O system. This consists of 4 main parts:</p><ul><li>Entities loader, this is a routine which tries to fetch the entities
(files) based on their PUBLIC and SYSTEM identifiers. The default loader
don't look at the public identifier since libxml2 do not maintain a
catalog. You can redefine you own entity loader by using
<code>xmlGetExternalEntityLoader()</code> and
<code>xmlSetExternalEntityLoader()</code>. <ahref="#entities">Check the
example</a>.</li>
<li>Input I/O buffers which are a commodity structure used by the parser(s)
</ul><p>The general mechanism used when loading http://rpmfind.net/xml.html for
example in the HTML parser is the following:</p><ol><li>The default entity loader calls <code>xmlNewInputFromFile()</code> with
the parsing context and the URI string.</li>
<li>the URI string is checked against the existing registered handlers
using their match() callback function, if the HTTP module was compiled
in, it is registered and its match() function will succeeds</li>
<li>the open() function of the handler is called and if successful will
return an I/O Input buffer</li>
<li>the parser will the start reading from this buffer and progressively
fetch information from the resource, calling the read() function of the
handler until the resource is exhausted</li>
<li>if an encoding change is detected it will be installed on the input
buffer, providing buffering and efficient use of the conversion
routines</li>
<li>once the parser has finished, the close() function of the handler is
called once and the Input buffer and associated resources are
deallocated.</li>
</ol><p>The user defined callbacks are checked first to allow overriding of the
default libxml2 I/O routines.</p><h3><aname="basic"id="basic">The basic buffer type</a></h3><p>All the buffer manipulation handling is done using the
<code>xmlBuffer</code> type define in <code><ahref="http://xmlsoft.org/html/libxml-tree.html">tree.h</a></code>which is a
resizable memory buffer. The buffer allocation strategy can be selected to be
either best-fit or use an exponential doubling one (CPU vs. memory use
trade-off). The values are <code>XML_BUFFER_ALLOC_EXACT</code> and
<code>XML_BUFFER_ALLOC_DOUBLEIT</code>, and can be set individually or on a
system wide basis using <code>xmlBufferSetAllocationScheme()</code>. A number
of functions allows to manipulate buffers with names starting with the
<code>xmlBuffer...</code> prefix.</p><h3><aname="Input"id="Input">Input I/O handlers</a></h3><p>An Input I/O handler is a simple structure
<code>xmlParserInputBuffer</code> containing a context associated to the
resource (file descriptor, or pointer to a protocol handler), the read() and
close() callbacks to use and an xmlBuffer. And extra xmlBuffer and a charset
encoding handler are also present to support charset conversion when
needed.</p><h3><aname="Output"id="Output">Output I/O handlers</a></h3><p>An Output handler <code>xmlOutputBuffer</code> is completely similar to an
Input one except the callbacks are write() and close().</p><h3><aname="entities"id="entities">The entities loader</a></h3><p>The entity loader resolves requests for new entities and create inputs for
the parser. Creating an input from a filename or an URI string is done
through the xmlNewInputFromFile() routine. The default entity loader do not
handle the PUBLIC identifier associated with an entity (if any). So it just
calls xmlNewInputFromFile() with the SYSTEM identifier (which is mandatory in
XML).</p><p>If you want to hook up a catalog mechanism then you simply need to
override the default entity loader, here is an example:</p><pre>#include <libxml/xmlIO.h>
