...
- Provide generic interfaces to Interface modules for abstracting the operations that can be performed by Processor modules
- Provide functionality for Processor modules to dynamically register/deregister as handlers for specific content (MIME) types at runtime.
See the below interfaces; Processor modules can register handlers for specific content types during module startup (or whenever deemed appropriate by the module). The content handlers need to provide functionality to save and retrieve content. Interface handlers can simply then retrieve a registered instance based on the content type of the data they need to handle. The Content Handler module will provide a default handler in the case that there are no handlers registered for a requested type. Most likely this will be the Unstructured Document handler. The module follows the prototype pattern for content handler instantiation. When registering a handler, a Processor module provides an instance of a handler. Then whenever the getContentHandler method is called, the Content Handler module will clone an instance of the handler for use by the caller.
...