[rabbitmq-discuss] Python Client for RabbitMQ/AMQP?

[Alexis Richardson]

Martin

Let's checkpoint a list of mismatches once M2 comes out, running it in
strict mode.

I agree it is very good we can cross check clients and servers, and
appreciate everyone's efforts!

alexis



On 8/23/07, Martin Ritchie <ritchiem at apache.org> wrote:
> Alexis,
>
> I'd be very interested in your list of mismatches with Qpid. I know
> the Qpid Java client deviates from the AMQP spec to fully be JMS
> compliant but I did add a property AMQP_STRICT which should turn all
> that off so you can use the JMS client that will fit on the standard
> 0_8 AMQP. If there is somthing I have missed then I will gladly fix
> it.
>
> Our long over due M2 release will be available with the next week or
> so. If you have been working with M1 then this is a major leap
> forward.
>
> I think it is great that our different groups can write clients and
> brokers and use each others clients/test suites to validate our own
> work.
>
> Cheers
>
> On 23/08/07, Alexis Richardson <alexis.richardson at cohesiveft.com> wrote:
> > Jeff
> >
> > We want to fix this.  Do you have any other examples of mismatch
> > between OpenAMQ and RabbitMQ?
> >
> > I think we've managed to nail down the ones for Qpid -- Matthias any comments?
> >
> > alexis
> >
> >
> >
> > On 8/23/07, Jeff Rogers <dvrsn at diphi.com> wrote:
> > > Alexis Richardson wrote:
> > >
> > > > BUT - modulo the spec version, any client should interoperate with any broker.
> > >
> > > I'm not sure if it is the differences in spec version or just
> > > incompletely or differently implemented servers but my limited
> > > experience has not borne this out.  I was working on a tcl client and
> > > ran into a number of small but annoying differences in how rabbitmq and
> > > OpenAMQ deal with things.  For example, rabbitmq requires an
> > > access.request call before accessing anything while openamq doesn't
> > > implement access.request at all and gives you a channel error if you
> > > even make the call.  On the side of rabbitmq doing things wrong, the
> > > authentication is completely screwy - the server response says that it
> > > only supports PLAIN authentication but the server only implements AMQPLAIN.
> > >
> > > Maybe this just points out a need for multiple independent clients to
> > > test against;  particularly in the case of the authentication rabbitmq
> > > seems to be making specific allowances for qpid even tho it appears qpid
> > > is not following the spec exactly.
> > >
> > > -J
> > >
> > >
> > > _______________________________________________
> > > rabbitmq-discuss mailing list
> > > rabbitmq-discuss at lists.rabbitmq.com
> > > http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> > >
> >
> >
> > --
> > Alexis Richardson
> > +44 20 7617 7339 (UK)
> > +44 77 9865 2911 (cell)
> > +1 650 206 2517 (US)
> >
> > _______________________________________________
> > rabbitmq-discuss mailing list
> > rabbitmq-discuss at lists.rabbitmq.com
> > http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> >
>
>
> --
> Martin Ritchie
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>


-- 
Alexis Richardson
+44 20 7617 7339 (UK)
+44 77 9865 2911 (cell)
+1 650 206 2517 (US)