Data Bindings Overview

Data bindings are utilized to specify 'handlers' for data that is received or processed by AlchemyPoint. Bindings generally provide one or more filtering options (a url, an e-mail address, a filename, etc.) and a series of ChainedActions and ChainedConditions. 'Messages' (HTTP requests, emails, files, etc.) received by the system that match a binding's filtering options will be processed by the embedded list of ChainedActions / ChainedConditions. This process should be familiar to anyone who has worked with webserver or appserver configuration.

One or more bindings may be specified within an InputConnector or ProtocolListener? , allow for different 'handlers' to be specified for specific types of data. For instance, one could create a FTPInputConnector that retrieves all files from a remote FTP server on a regular interval, providing a number of different bindings for processing individual file types ("*.tar.gz", "*.zip", etc.).

Bindings Object

• Bindings - Embedded within an InputConnector or one of the ProtocolListeners, this object specifies one or more data Binding? objects. These Bindings determine what should be done with data received by the AlchemyPoint system.

Example Abstract Object Definition

... directly within an InputConnector or ProtocolListener? object:

<Bindings>
        <Binding ... >
        ...
</Bindings>

Supported Binding Types

• WebBinding - A HTTP input binding, used within a HTTPFullDuplexListener or HTTPInputConnector.

• MailBinding? - A mail input binding, used within a SMTPInputListener? or MailInputConnector.

• FileBinding? - A file input binding, used within a FileInputConnector or FTPInputConnector.

• IMBinding? - An instant messenger input binding, used within an IMConnection.

• ORMQBinding? - An ORMQ? input binding, used within an ORMQInputConnector or ORMQSubscription.