DOM resolver subsystem

From COLLADA Public Wiki
Revision as of 22:37, 20 March 2007 by Elf (talk | contribs) (→‎Purpose: little copy edit)
Jump to navigation Jump to search

Summary: The resolver subsystem manages the resolution of URIs based on a URI's scheme and filename extensions.


The resolver subsystem allows for custom URI resolvers to be written and added to the COLLADA DOM. These resolvers can be used to load various types of external references-- for example, binary representations of mesh data--or to provide access to different data systems--for example, using a database to access elements.

Default behavior

By default, the COLLADA DOM has only two resolvers. The main resolver, daeLIBXMLResolver resolves elements from COLLADA documents (.dae or .xml) with the file or http URI scheme. This can resolve elements from the same docuemnt or external document references.

The newly added DOM raw resolver class, daeRawResolver, resolves only .raw files with the file URI scheme. A .raw file contains COLLADA source element float_array and int_array data in binary form.

Instantiating an object of a class that inherits from daeURIResolver adds a custom resolver to the COLLADA DOM.

How it works

The base class daeURIResolver contains a static array of resolvers named _KnownResolvers. The constuctor for daeURIResolver adds a reference to this to this list of resolvers. When a DOM URI class attempts to resolve itself it searches through the _KnownResolvers list for a resolver that matches it's URI scheme and file extension. When an appropriate resolver is found, the resolver is then asked to resolve the current URI.

Related classes and functions