Steven Shaw wrote:
On 15/09/06, Robert Greig <[EMAIL PROTECTED]> wrote:
I think we agree that we need to expose functionality that goes beyond
JMS. The question is whether we can do this though extension points to
JMS or whether we need a separate API.
Perhaps both.
I agree with this view. The different ways of exposing functionality
need not be mutually exclusive.
Support at the 'protocol' level makes it easier for the full flexibility
of AMQP to be exploited in perhaps unanticipated ways.
As an example, pulled out the air, imagine a particular use case wants
to set up a single queue with several bindings. Rather that trying to
anticipate all these sorts of usage patterns from the start a more
directly exposed protocol layer would make these easy to compose from
the protocols own building blocks.
However JMS is clearly the first choice for the vast majority of
messaging based systems written in java, so allowing these system to
exploit the protocol through API extensions or configurable semantics or
mappings is also going to be important.
