On 07/06/07, Jonathan Robie <[EMAIL PROTECTED]> wrote:
Isn't the obvious solution to have two APIs?
OK, so this leads back to one of my other points: are both APIs going to be equivalent in terms of capabilities? Is the JMS API going to be some poor cousin of the other API? Or are we going to use the "extended JMS" approach to allow full use of AMQP capabilities via an API that is fundamentally JMS-like. If both APIs are going to have equivalent power, then that certainly is workable. But I would still question the value of it (certainly I would say the opportunity cost is too high).
Of course support for JMS is crucially important. But if that's all we do, I think we've missed a rare opportunity to dramatically simplify interoperable computing across languages and platforms.
I don't see how the API affects interop across platforms. We can interop today between Java JMS and C++ and Python (protocol issues notwithstanding :-)).
If all we care about is JMS, let's stop spending time thinking about anything else.
The whole point of this discussion is about how we expose AMQP functionality in Java. It is not about bog standard JMS compliance. RG
