[Stackless] stackless socket, curiouser and curiouser

Paul Sijben sijben at eemvalley.com
Mon Feb 26 17:46:24 CET 2007

Do^h, I am feeling very stupid.  My loop and my problem with the test
prog was the same issue. You can not do a recvfrom  on a non-blocking
socket, and /unlike/ the regular socket, on asyncore sockets are
non-blocking /by default! /Setting the stacklesssocket I made to
blocking sorted that problem.

Now I seem to be losing packets. wireshark tells me they are delivered
to the machine, however my not blocking recvfrom does not return. But
this is not in the test program only in the full one.

So tomorrow I'll compare it the other way around.

One question, what would cause stackless.run() to block?


Paul Sijben wrote:
> working on it. for some strange reason the stacklesssocket tells me
>     res = self.s.recvfrom(8192)
> error: (11, 'Resource temporarily unavailable')
> yet I seem to have all the socket related stuff in the little script...
> I'll post the script when it works.
> Richard Tew wrote:
>> On 2/26/07, Paul Sijben <sijben at eemvalley.com> wrote:
>>>  etc.... Well that tells me that the recvfrom throws me back down the
>>> function stack. I am baffled as to why.
>>>  Can someone please explain this to me? (and of course what I should
>>> to to
>>> get the expected result)
>> Hi Paul,
>> Can you please provide a standalone script which when run reproduces
>> this?
>> Thanks,
>> Richard.

Paul Sijben                    	tel: +31334566488
Eemvalley Technology       	fax: +31334557523
the Netherlands                	http://eemvalley.com    

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.stackless.com/pipermail/stackless/attachments/20070226/a7527d1e/attachment.htm>
-------------- next part --------------
Stackless mailing list
Stackless at stackless.com

More information about the Stackless mailing list