Robert Greig wrote:
On 06/06/07, Robert Godfrey <[EMAIL PROTECTED]> wrote:
Allowing users who are committed to AMQP (rather than to JMS) to use
an AMQP API does not upset me in the same way it does you.
It's forcing users to make that decision to commit to AMQP that
bothers me. I think you should be able to choose to use proprietary
features in isolated pockets of code within the context of an
otherwise standards-based implementation.
If a user wants to use JMS, how does the presence of an alternative
force them to do anything different than what they would do if there is
only one Java API?
Jonathan
