Each protocol is implemented in a Remote DS module.
As the Components Manager searches a component, each DS has to return a response. Null if the DS can't find the component requested. The response is asynchronous, so that the protocol can perform a network search.
When the Components Manager has all the responses of all DS, then the Components Manager selects one DS to perform components connection.
You can change the Components Manager's strategy of connection, for example you prefer remote components before local components.
A local component is connected to a proxy that represents the remote component.
The Remote DS, which is the protocol, is in charge of delivering the message to the real component instance.
This is based on our first Remote DS implementations (simpleUDP and simpleTCP).
Next: Advanced possibilities
Last modified: $Date: 2008-08-25 11:25:14 +0200 (Mon, 25 Aug 2008) $