XML Parser Implementation Considerations
The XML Parser for Windows CE .NET can be implemented in several different configurations, depending on your needs. The features have been componentized into specific XML technologies, which allow you to select the proper level of XML support for your device.
The XML Minimal Parser provides minimal Simple API for XML (SAX)-based parsing of data. This feature is a good choice for platforms that need an extremely small footprint, but still need to provide some XML functionality. The XML Minimal Parser is for devices that do not require extensibility, or highly specialized applications.
For enterprise-level devices, choose the full complement of XML parser functionality. The features necessary for full XML support are XML Core Services and Document Object Model (DOM), XML HTTP, XML Query Language, XML Stylesheet Language Transformation, and the full XML SAX. This group of features provide increased portability of applications between the desktop version of MSXML and devices using Windows CE .NET. The full complement of XML features increases support for databases and Web services.
The following tables show the core and networking components that implement XML Parser functionality on Windows CE .NET. To implement the XML Parser, you must use one or more of the core components and exactly one networking component.
|Core component||Sysgen variable||Description|
|xmlminisax||SYSGEN_MSXML_MINI||Provides the smallest possible Extensible Markup Language (XML) configuration for devices that require some XML parsing but have extremely limited resources. This component supports SAX-based parsing only, but does not perform Document Type Definition (DTD) validation or element resolution. It also does not support the MXXMLWriter class and is not callable from Microsoft Visual Basic®. This option must be the only core XML component specified; no other components rely on it. Selecting this component automatically selects the xmlnetmini networking component.|
|xmldom||SYSGEN_MSXML_DOM||Supports the basic DOM for MSXML. This component performs DTD and schema verification on documents if desired and includes XML error strings not included in xmlminisax. It also supports schema caching. This component is required by all other core XML components except xmlminisax. Selecting this component automatically selects the xmlnetful networking component.|
|xmlhttp||SYSGEN_MSXML_HTTP||Implements the XMLHTTP object. This object enables web services.|
|xmlsax||SYSGEN_MSXML_SAX||Provides SAX support for configurations in which xmldom is included. Unlike xmlminisax, xmlsax performs DTD validation of documents, includes MXXMLWriter, and can be used from Visual Basic.|
|xmlxql||SYSGEN_MSXML_XQL||Provides support for the XML Query Language (XQL).|
|xmlxslt||SYSGEN_MSXML_XSLT||Provides XML Stylesheet Language Transformation (XSLT) support. Requires the xmlxql component.|
|xmlmime||SYSGEN_MSXML_MIMEVIEWER||Allows Internet Explorer to display XML documents without the need for writing script to output XML content to DHTML objects. In addition, the XML Multipurpose Internet Mail Extension (MIME) viewer will automatically apply any XML style sheets associated with the XML document it processes.|
|xmlnetfull||Relies on WinInet and Urlmon to perform network operations, such as downloading DTDs from remote servers. This component is required for xmlhttp and asynchronous parsing support.|
|xmlnetmini||Uses httplite, which is a stripped down version of WinInet and is intended for devices that have resource limitations. If xmlnetmini is selected, asynchronous downloads are not supported. Attempts to set the async property in DOM will return E_NOTIMPL.|
The XML Parser for Windows CE does not support the following features in any componentization configuration:
- The ServerXMLHTTP object.
- The IWinHttp interface, which is set through setServerHttpRequest.
- Data Source Objects (DSO) support.
- Data island support.
- The FreeThreadedDOMDocument object.
- The XSLTemplate and IXSLProcessor interfaces. MSXML 3.0 supports XSLT through the transformNode method, but it does not support template caching.
- Backward compatibility with the MSXML DOM supported by Microsoft Internet Explorer 4.0 for Windows CE Internet browser.
For more information about XML development and using the MSXML Parser, see this Microsoft Web site.
Last updated on Friday, April 09, 2004
© 1992-2003 Microsoft Corporation. All rights reserved.