Message 169646 - Python tracker

➜

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	neologix
Recipients	jarvisliang, neologix, pitrou
Date	2012-09-01.16:53:59
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1346518440.69.0.909465016445.issue15523@psf.upfronthosting.co.za>
In-reply-to

Content
> So when calling close_request to deallocate the socket, it will > always be waiting to read response until response data is available. > It seems like an issue in SokcetServer.py library. Hum, I don't see what you mean. Even if there is still data in the receive socket buffer, socket.clos() shouldn't block. Actually, it should result in a RST being sent. Could you describe your problem more precisely (with a code snippet it would be better)?

> So when calling close_request to deallocate the socket, it will 
> always be waiting to read response until response data is available. 
> It seems like an issue in SokcetServer.py library.

Hum, I don't see what you mean.
Even if there is still data in the receive socket buffer, socket.clos() shouldn't block. Actually, it should result in a RST being sent.
Could you describe your problem more precisely (with a code snippet it would be better)?

History
Date	User	Action	Args
2012-09-01 16:54:00	neologix	set	recipients: + neologix, pitrou, jarvisliang
2012-09-01 16:54:00	neologix	set	messageid: <1346518440.69.0.909465016445.issue15523@psf.upfronthosting.co.za>
2012-09-01 16:54:00	neologix	link	issue15523 messages
2012-09-01 16:53:59	neologix	create