> > I do not particularly see the need for an API which is neither JMS that > doesn't look exactly like the model layers of AMQP [that is the API need > not > expose all the 0-10 features for connection establishment, session > maintenance etc... those are functions of the client library and shouldn't > be exposed to the application programmer - For those familiar with AMQP > 0-10 > I think the API should provide hooks into all of Layer 4... with > abstractions for the lower layers].
+1 I have the same view point. Besides if you make a *very* thin client that's close to the wire protocol I really doubt people want to go between different client libraries. The decoding/encoding part would be the difference. Unless it is written abysmally, I really doubt there is much of a difference in terms of performance. However as Rob points out, the motivation for changing the client lib might come from some cool vendor specific hack :) anyways when u use that you will not be able to move again. Rajith
