[rabbitmq-discuss] py-amqplib being reworked

[Michael Arnoldus]

Hi Barry,

This is interesting work. We are currently using the Qpid M1 python  
client and aren't entirely satisfied, especially with error handling.  
As we're about to decide on a new client library py-amqplib has been  
considered. Until now it hasn't really been an option due to the lack  
of support for timeout, basic.reject etc. However with this latest  
message I want to consider it again.

The other candidate we have considered is naturally the Qpid M2.1 or  
M3 pythin lib. Do you have any idea about the difference? If not then  
maybe you can tell me what let you to write py-amqplib instead of  
using the Qpid client? I remember in the beginning something about  
specifically going for a unthreaded library, but it seems you have  
given that up (which incidentally makes very much sense in my book  
considering the AMQP protocol).

Regards,

Michael Arnoldus

On Dec 1, 2008, at 22:36 , Barry Pederson wrote:

> I've had some time to work on py-amqplib over the holiday, and
> have done some serious rearranging of code.  The biggest
> thing has been to breakup the monstrosity that was there before to
> better reflect how the protocol is layered.
>
> I've also started working on features people have been having problems
> with or needs for, like non-blocking waits, flow-control, and handling
> of returned messages.
>
> It's still got a ways to go, needs lots of testing, and I still may  
> make
> some large changes, but for anyone interested I've started a new
> Mercurial repository at:
>
>    http://hg.barryp.org/py-amqplib-devel/
>
> The API is essentially unchanged so old users of amqplib
> *should* still work.
>
> The Connection() initializer has a "use_threading" option
> that defaults to False, giving the old single-threaded behavior,
> but with True it creates a helper thread that allows for
> timeouts and flow control.
>
> I'm not happy with some of the details about waiting and handling
> flow-control and returned messages, and error handling needs work, so
> it's definitely a work-in-progress (actually, it always has been, but
> it's even more so for the near future).
>
> 	Barry
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1912 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20081201/c8fbbc16/attachment.bin