John O'Hara wrote:
This is just one of those bullets that we have to bite on.
AMQP is "getting there", seeing what the low level API shapes out as
is part of the stabalising process.
Top down design / bottom up design -- need both at the same time in
my experience.
I agree, but I still think its premature to try and standardise the
translation of the AMQP application level protocol into language
specific bindings. For one thing I'm not convinced there is significant
user demand yet for such a standardisation. Any standardisation also
takes time and effort and the AMQP working group should in my opinion
focus on getting the protocol itself to the required state by 1.0.
Within the Qpid project, where there are existing standard APIs that are
applicable we are all agreed that providing implementations that use
AMQP is beneficial. I think we all also agree that we want the various
clients to 'fit' well as part of a larger 'product'.
At least as important for consumer choice as the existence standard APIs
is the availability of high-quality, mature, well documented and easy to
use client libraries and I think we should initially focus on providing
that.
