This section contains information about the Client Server component which forms the basis for all messaging functionality. The core is build around a dynamic messaging architecture that borrows heavily from the ACE library ‘The ADAPTIVE Communication Environment’ and concepts defined by Prof. Douglas C. Schmidt. There are plentiful of documentation on the ACE website describing core design patterns. Design patterns are also borrowed from TAO which is an realtime ORB built on ACE.

All in all the component is the foundation on which WebServer, SOAP, WebServices and ebXML MHS, JMS, etc. may be built.

Major characteristics

Pluggable protocols:

• Dynamically loaded.
• Transport: for different transport protocols, connections are cached for reuse
• Connector: encapsulates connection establishments
• Acceptor: encapsulates accepting incomming connection requests
• Profile: encapsulates endpoints and related information
• MProfile: handles multiple Profiles which is used for fault tolerance.

Strategies:

Core behaviour is factored out into Strategy classes and object, such as
   determining which threading policy should be used (thread per connection or...)
   how incomming messages should be handled
   which endpoint should be selected next when a connection has failed.

Messages

Different types of Messages are created by MessagesFactories and dynamically bound to acceptors etc.

Others

• Timeout handling
• Different types of invocations are handled by Invocation specific object
• Targets delgates to backend Stub