And I do agree, there needs to be a slightly higher level client API, to make this very low-level direct protocol API usable to code against. In Java I believe that it is JMS + horizontal extensions, in other languages, something similar wrt JMS licensing issues, or better if you come up with a nicer abstraction.
On 20/08/07, Rupert Smith <[EMAIL PROTECTED]> wrote: > > On 20/08/07, Arnaud Simon <[EMAIL PROTECTED]> wrote: > > > I like what Rupert is proposing but it may be too low level. Rupert you > > are saying that the current API does not expose the AMQP ping mechanism. > > Is that all? Can you provide an exhaustive list of the AMQP features > > that are not exposed? > > > > As a typing exercise yes, but not one I am inclined to do. I shall instead > furnish you with a procedure for creating this list. Look at the protocol > XML, compare every method marked as <chassis name="server" ...>, and look at > the API to see if it is there or not. Look for every method marked as > <chassis name="client ...> and ask where is its 'delegate' interface. > > On the client side, really only 'messageTransfer' is there. > > The comm layer does provide everything, as it is generated from this XML. >
