I shall give a few concrete examples of protocol 'methods' that I cannot see
in your API, as this is what you have asked me for. Picked at random, and
not a complete list, simply to prove the point that not everything is there:

session.ping
session.closed
message.qos
... (there are more, its simply a case of comparing your API to the XML)


Watching the debate, I think you guys are actually quite close to each other. For example, message.qos -- voted out and replaced with the flow commands in message class
session.ping -- has been renamed to no op I believe
...

So I think the debate is somewhat connected to 0-10. From what I can see, by the time 0-10 is completely voted and the client is done there should be a 1:1 mapping, with some
utility classes/functions. I might be wrong, but that is my take.

It might be useful doing a review once all the 0-10 votes are complete,I for one have enjoyed following the debate. It might also be worth linking and posting more of the spec
on our wiki. Maybe even link to the amqp.org JIRA on spec issues.
Carl.


Reply via email to