[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: LDAP broker

>it should be made of a number of local agents and remote agents. The remote
>agent is the process that gets the data from the data source or writes the
>data to the data source. the local agents, could also be called connectores
>are responsible for connecting to the remote agents. The broker is using
>kind of dispatcher. It gets from the dispatcher a pair of agents. One agent
>getting data and one or more agent writing data. A configuration utility
>tells the broker how it should combine the data. It should also be possible
>to filter out data before handling it over to other data sources.

This seems like it could be greatly simplified by using some type of MOM
(Message Oriented Middleware), such as xmlBlaster
(http://www.xmlblaster.org) so that 'broker agents' could use one of
many standard protocols (CORBA, RMI, XML-RPC) to inform the
system-as-a-while of data-in-waiting, and relevant 'broker agents' would
simply subscribe to the data patterns/streams they are interested in. 
Then you'll have the power of proven technologies such as XPath at your
disposal as well as the flexibility of both volatile-point-in-time and
store-and-forward types of data transfer.