I *suspect* that an AMQP API will serve the needs of most anti-JMS
customers, or at least be enough for them to get started while we figure
out what (if any) other higher-level API features we want. If not the
AMQP layer will make it *much* easier to implement and maintain multiple
"personality" layers on top.
Cheers,
Alan.
Just to add to Alans note. There are several folks who want to utilise the
full power of AMQP and are not too crazy about AMQP.
I don't like to tell our customers that they have to wait till we stabilize
the API. These early adopters are doing us a favor by showing some faith in
AMQP and Qpid.
Why do we want to discourage them ??
Also as Rob points out there is only a certain amount of features that u can
expose through an extended JMS API. So I don't want to force our customers
to use JMS when they are willing to use something else.
For example some people like to use the message.get functionality. This
cannot be expressed in JMS as rob points out.
On the same token I agree that people who want to use JMS should be able to,
and we should allow extensions where it is meaningful.
I think we have agreement here.
Regards,
Rajith
