[zeromq-dev] Python / ZMQ - EAGAIN
Antonio Teixeira
eagle.antonio at gmail.com
Tue Apr 24 10:15:17 CEST 2012
Good Morning.
Well i tried
http://pastebin.com/QdS9gbN6
but :
Normal ZMQ - EAGAIN Raised
Green ZMQ - EAGAIN Raised
On
Python 2.6.5 (r265:79063, Apr 16 2010, 13:09:56)
PyZMQ
>>> zmq.__version__
'2.1dev'
ZMQ
v2.2.0, from 2012/04/04
2012/4/23 MinRK <benjaminrk at gmail.com>
>
>
> On Mon, Apr 23, 2012 at 09:37, Antonio Teixeira <eagle.antonio at gmail.com>wrote:
>
>> Ok So here I'm one more time :)
>>
>> In my async framework I do use zmq.noblock ( Poller is not green enough
>> :D ) to avoid blocking when doing a recv() or send()
>>
>> The question is dead simple but i couldn't find a way to differentiate
>> this situation.
>>
>> How can i distinct between EAGAIN raised because the socket is not ready.
>>
>> Or
>>
>> EAGAIN raised because on a REQ socket i'm calling send() instead of recv()
>>
>
> Easy: EAGAIN is not raised on a REQ socket calling send when it should be
> recv, EFSM is.
>
>
>>
>>
>> Regards
>> Antonio
>>
>>
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>
>>
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20120424/56690db6/attachment.htm>
More information about the zeromq-dev
mailing list