On 07/06/07, Jonathan Robie <[EMAIL PROTECTED]> wrote:
Robert Greig wrote:
> 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?
The user may want to use JMS. But may not want to preclude using
AMQP-specific functionality at a future date or now but only in some
parts of the codebase. If to use AMQP-specific functionality the user
cannot use "extended JMS" then you are forcing him to choose a
proprietary API.
RG
