asynchat - operation could not complete w/ blocking

Fredrik Lundh fredrik at pythonware.com
Wed Mar 8 13:28:17 CET 2006


(possible duplicate; reposted due to mail server problems)

"Andreas R." `wrote:

>> what sendall method ?  to get proper output buffering with asynchat, use
>
> Search for sendall here:
> http://svn.gna.org/viewcvs/openrts/trunk/openrts/client/networksend.py?rev=67&view=markup
>
> That's what I was told to use here:
> http://groups.google.no/group/comp.lang.python/browse_thread/thread/e8615b50ea990a5f/0a30540bd8ec9db5
>
> That's not correct?

nope.  asyncore uses it's own send implementation, and asynchat implements
proper buffering on top of asyncore's send via the push methods.

the reason that you could call sendall appears to be that asyncore gives you
access to *all* socket object attributes via dynamic inheritance, and nobody
thought of filtering out the sendall method (which is a rather recent addition
to the socket layer).  this should probably be fixed.

</F> 






More information about the Python-list mailing list