# The XML C parser and toolkit of Gnome ## I/O Interfaces

Developer Menu
Main Menu Reference Manual Code Examples XML Guidelines Tutorial The Reader Interface ChangeLog XSLT Python and bindings libxml2 architecture The tree output The SAX interface Memory Management I/O Interfaces The parser interfaces Entities or no entities Namespaces Upgrading 1.x code Thread safety DOM Principles A real example flat page, stylesheet
API Indexes
Alphabetic Constructors Functions/Types Modules Symbols
Related links
Mail archive XSLT libxslt DOM gdome2 XML-DSig xmlsec FTP Windows binaries Solaris binaries MacOsX binaries C++ bindings PHP bindings Pascal bindings Ruby bindings Tcl bindings Bug Tracker
Table of Content: General overview The basic buffer type Input I/O handlers Output I/O handlers The entities loader Example of customized I/O ### General overview The module `xmlIO.h`providestheinterfaces to the libxml2 I/O system. This consists of 4 main parts: Entities loader, this is a routine which tries to fetch theentities(files) based on their PUBLIC and SYSTEM identifiers. The defaultloaderdon't look at the public identifier since libxml2 do not maintainacatalog. You can redefine you own entity loader byusing`xmlGetExternalEntityLoader()`and`xmlSetExternalEntityLoader()`.Check theexample. Input I/O buffers which are a commodity structure used by theparser(s)input layer to handle fetching the informations to feed theparser. Thisprovides buffering and is also a placeholder where theencodingconverters to UTF8 are piggy-backed. Output I/O buffers are similar to the Input ones and fulfillsimilartask but when generating a serialization from a tree. A mechanism to register sets of I/O callbacks and associate themwithspecific naming schemes like the protocol part of the URIs. This affect the default I/O operations and allows to use specificI/Ohandlers for certain names. The general mechanism used when loading http://rpmfind.net/xml.htmlforexample in the HTML parser is the following: The default entity loader calls`xmlNewInputFromFile()`withthe parsing context and the URIstring. the URI string is checked against the existing registered handlersusingtheir match() callback function, if the HTTP module was compiledin, it isregistered and its match() function will succeeds the open() function of the handler is called and if successfulwillreturn an I/O Input buffer the parser will the start reading from this buffer andprogressivelyfetch information from the resource, calling the read()function of thehandler until the resource is exhausted if an encoding change is detected it will be installed on theinputbuffer, providing buffering and efficient use of theconversionroutines once the parser has finished, the close() function of the handleriscalled once and the Input buffer and associated resourcesaredeallocated. The user defined callbacks are checked first to allow overriding ofthedefault libxml2 I/O routines. ### The basic buffer type All the buffer manipulation handling is done usingthe`xmlBuffer`type define in `tree.h`which isaresizable memory buffer. The buffer allocation strategy can be selected tobeeither best-fit or use an exponential doubling one (CPU vs. memoryusetrade-off). The values are`XML_BUFFER_ALLOC_EXACT`and`XML_BUFFER_ALLOC_DOUBLEIT`,and can be set individually or on asystem wide basis using`xmlBufferSetAllocationScheme()`. A numberof functions allows tomanipulate buffers with names starting withthe`xmlBuffer...`prefix. ### Input I/O handlers An Input I/O handler is a simplestructure`xmlParserInputBuffer`containing a context associated totheresource (file descriptor, or pointer to a protocol handler), the read()andclose() callbacks to use and an xmlBuffer. And extra xmlBuffer and acharsetencoding handler are also present to support charset conversionwhenneeded. ### Output I/O handlers An Output handler `xmlOutputBuffer`is completely similar toanInput one except the callbacks are write() and close(). ### The entities loader The entity loader resolves requests for new entities and create inputsforthe parser. Creating an input from a filename or an URI string isdonethrough the xmlNewInputFromFile() routine. The default entity loader donothandle the PUBLIC identifier associated with an entity (if any). So itjustcalls xmlNewInputFromFile() with the SYSTEM identifier (which ismandatory inXML). If you want to hook up a catalog mechanism then you simply need tooverridethe default entity loader, here is an example:
    #include <libxml/xmlIO.h>

    xmlExternalEntityLoader defaultLoader = NULL;

    xmlParserInputPtr
    xmlMyExternalEntityLoader(const char *URL, const char *ID,
                                   xmlParserCtxtPtr ctxt) {
        xmlParserInputPtr ret;
        const char *fileID = NULL;
        /* lookup for the fileID depending on ID */

        ret = xmlNewInputFromFile(ctxt, fileID);
        if (ret != NULL)
            return(ret);
        if (defaultLoader != NULL)
            ret = defaultLoader(URL, ID, ctxt);
        return(ret);
    }

    int main(..) {
        ...

        /*
         * Install our own entity loader
         */
        defaultLoader = xmlGetExternalEntityLoader();
        xmlSetExternalEntityLoader(xmlMyExternalEntityLoader);

        ...
    }
1. ### Example of customized I/O This example come from areal use case,xmlDocDump() closes the FILE * passed by the applicationand this was aproblem. The solutionwasto redefine anew output handler with the closing call deactivated: First define a new I/O output allocator where the output don't closethefile:
       xmlOutputBufferPtr
       xmlOutputBufferCreateOwn(FILE *file, xmlCharEncodingHandlerPtr encoder) {
           xmlOutputBufferPtr ret;

           if (xmlOutputCallbackInitialized == 0)
               xmlRegisterDefaultOutputCallbacks();

           if (file == NULL) return(NULL);
           ret = xmlAllocOutputBuffer(encoder);
           if (ret != NULL) {
               ret->context = file;
               ret->writecallback = xmlFileWrite;
               ret->closecallback = NULL;  /* No close callback */
           }
           return(ret);
       }
2. And then use it to save the document:
       FILE *f;
       xmlOutputBufferPtr output;
       xmlDocPtr doc;
       int res;

       f = ...
       doc = ....

       output = xmlOutputBufferCreateOwn(f, NULL);
       res = xmlSaveFileTo(output, doc, NULL);
Daniel Veillard