h1 Proposed Architecture
The following diagram depicts the architecture for the client and broker.
The idea is to auto generate and share as much code as possible between the broker and the client.
-------------------------------
JMS for Client/ Broker Logic
-------------------------------
Qpid Layer( Client/Broker)
Invoker – For out going
Delegate – For incomming
-------------------------------
Communication Layer
-------------------------------
The communication layer will be common to both client and broker.
The Qpid Layer contains handlers that are both common to client and broker as well as Client and Server specific classes.
The 3rd Layer is where the message processing logic will be implemented.
- For Client there will be a thin wrapper called Qpid API to mask around the Invoker and expose methods by class.
The client will use the Delegate to handle incomming events.
- This can be used to implement JMS on top.
- Or application logic directly on top of the Qpid API.
- The Broker will build it's logic around the Invoker and Delegate.
h2 Invoker and Delegate
Invoker and Delegate are generated classes that contains all the methods in the spec.
To call a method you use the Invoker and to handle a method you use the Delegate.
h2 Multi Version Support
