Dave,
Thankyou. Regarding websockets, I'm very worried that you want to map
AMQP frames to websocket frames. This makes it impossible for anyone
to then use one of the many tcp to websocket gateways, so reducing
interoperability, and requiring deep broker integrations, etc. In some
ways this point mirrors the discussion we had about TLS in AMQP. It
does slightly complicate writing a js client, but very very slightly
(one has to hold onto the last few bytes in a buffer and append them
to the next buffet). Frankly, given that it's very hard to write a js
client in any event, this is exceedingly minor.
Raphael Cohn
Chief Architect
StormMQ Limited
UK Office:
Gateshead int'l Business Centre, Mulgrave Terrace, Gateshead, NE8 1AN,
United Kingdom
Telephone: +44 845 3712 567
Registered office:
16 Anchor Street, Chelmsford, Essex, CM2 0JY, United Kingdom
StormMQ Limited is Registered in England and Wales under Company Number 07175657
StormMQ.com
On 18 Apr 2013, at 00:09, David Ingham <> wrote:
> A few folks have asked me for my notes from the Redmond workshop that was held back in February so here they are attached. They are a little raw I'm afraid. There is reference to the AMQP management spec in these notes. Rob Godfrey, Rob Dolin and I have been iterating on that quite a bit since the workshop and I suspect that we'll have something to distribute for review within the next couple of weeks.
>
> Thanks,
> Dave.
> <mime-attachment>
> <2013.02-AMQP-TechnicalWorkshop-Redmond-Notes-Public.pdf>
