On 20/08/07, Arnaud Simon <[EMAIL PROTECTED]> wrote: > > > 3. Use of the inverse symmetry of the API so that the outgoing interface > > that the client calls, is identical to the incoming interface that the > > broker routing layer implements. > > This is a requirement for the common layer and I think that it already > does that, doesn't it?
Yes, but best way to have alternate implementations of things is through interfaces. Comm layer does look like it is leaning towards allowing this, but it defines stuff in terms of concrete classes. All I've really done is pull the exact same API out into a clean set of interfaces + factories, primarily with the intent of doing this sort of stuff. > 4. Be language neutral, that is a suitable API for implementing in any of > > our target languages. Will assume OO as a base-line. > > I am not sure that this is realistic and this should be left to AMQP to > provide such an API not to Qpid. > Also, again. I'm thinking about a clean modular design for our implementation, Qpid, not about a wonderful API for AMQP.
