Speaking for myself, lots of AMQP clients would be good. I'd be very
happy to see STOMP clients too. Basically: clients for messaging
protocols ftw.
alexis
I also think we should start out by building the lower level libraries
(codecs etc) which may be more generally useful for people who are
trying to build AMQP 1-0 rather than complete clients - we can create
building blocks, and then maybe complete clients... however allowing
people to take the abstract code and integrate it into their existing
clients will also be useful.
For me having a standard C library ("libamqp") would be a fantastic
start, and a leg-up to anyone who wanted to build a client in a
scripting language.
As an aside, I should hopefully soon be able to make the codec that I
wrote in Java for 1-0 (which was used for the demo at the F2F) more
generally available.
Cheers,
Rob
Fine by me...
On Jun 14, 2010 6:17 PM, "hi...@hiramchirino.com" <chi...@gmail.com> wrote:
Yeah me too. But perhaps we should just focus on AMQP clients on this
list as that scope is large enough on it own. Perhaps we should roll
out a STOMP list too though. There are lots of STOMP clients out
there but no central mailing list for them AFAIK.
On Jun 14, 1:02 pm, Alexis Richardson <ale...@rabbitmq.com> wrote: > Go for it Hiram. > > Speaking ...
> On Mon, Jun 14, 2010 at 5:53 PM, hi...@hiramchirino.com
> > > > <chir...@gmail.com> wrote: > > Membership list is up to 22 sounds like it may be time to kic...
Membership list is up to 22 sounds like it may be time to kick off
this list? Perhaps we should start by clarifying what are the goals
and expectations of the folks participating in the list?
Well, the Codehaus mailing lists are kind of central.
Also, we should not start from zero:
http://old.nabble.com/Stomp-1.1-td27502788.html
This said, I agree that this should stay separate from AMQP discussions.
Let's continue STOMP discussions on stomp-spec...
Cheers,
Lionel