This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mmw
Recipients giampaolo.rodola, josiah.carlson, josiahcarlson, mmw, rhettinger
Date 2010-08-26.02:33:07
SpamBayes Score 1.6618976e-06
Marked as misclassified No
Message-id <AANLkTinPqXDj2OJ6Kc23UGUrEtzJW3tu4jG15YHqcZF6@mail.gmail.com>
In-reply-to <1282776314.87.0.880071687075.issue9686@psf.upfronthosting.co.za>
Content
First it depends on the socket type but might use a select call, secondable
raise on a socket.error, thirdable you could call the close_handle with the
message and let the guys if he would like to retry, network connection might
be capricious especially for client connected through a wifi network or
behind some firewall blocking port

the asyncchat is a looper if you don't let him catch the exception you just
create an infinite loop, this API needs a stronger model.

On Wed, Aug 25, 2010 at 3:45 PM, Giampaolo Rodola'
<report@bugs.python.org>wrote:

>
> Giampaolo Rodola' <g.rodola@gmail.com> added the comment:
>
> Could you provide a code sample which demonstrates the problem?
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue9686>
> _______________________________________
>
Files
File name Uploaded
unnamed mmw, 2010-08-26.02:33:06
History
Date User Action Args
2010-08-26 02:33:09mmwsetrecipients: + mmw, rhettinger, josiahcarlson, giampaolo.rodola, josiah.carlson
2010-08-26 02:33:07mmwlinkissue9686 messages
2010-08-26 02:33:07mmwcreate