Oh, I see. Use STOMP to shove messages into RabbitMQ, and then you can
do whatever you like. I thought Phil was talking about using AMQP
directly. Writing a conformant/correct AMQP client is pretty hard, and
a lot of work, hence why I asked.
frank
On 26 November 2013 14:16, Sven Van Caekenberghe <sven@stfx.eu> wrote:
>
> On 26 Nov 2013, at 14:00, Frank Shearar <frank.shearar@gmail.com> wrote:
>
>> On 26 November 2013 12:21, phil@highoctane.be <phil@highoctane.be> wrote:
>>
>>> On the front of interoperability, I personally have chosen to go the
>>> RabbitMQ route, it allows me to wire all kinds of things together with some
>>> room for scale.
>>
>> What are you using on the Smalltalk side? I know Tony Garnock-Jones
>> did some basic parsing of AMQP, but I'm unaware of anything more than
>> that. Do you FFI to the C client library? Something else?
>>
>> frank
>
> I think Phil plans on using Stamp
>
> � https://github.com/svenvc/docs/blob/master/neo/stamp.md
>
> it is a pretty simple and easy to understand interface.
>
> Sven
>
>