Velocity Reviews

Velocity Reviews (http://www.velocityreviews.com/forums/index.php)
-   Python (http://www.velocityreviews.com/forums/f43-python.html)
-   -   Socket Programming (http://www.velocityreviews.com/forums/t620257-socket-programming.html)

srinivasan srinivas 06-14-2008 09:38 PM

Socket Programming
 
Hi,
Is there any way(method) to find whether the socket got closed or not??
Thanks,
Srini


Best Jokes, Best Friends, Best Food and more. Go to http://in.promos.yahoo.com/groups/bestofyahoo/

Jeff McNeil 06-15-2008 01:55 AM

Re: Socket Programming
 
On Jun 14, 5:38*pm, srinivasan srinivas <sri_anna...@yahoo.co.in>
wrote:
> Hi,
> Is there any way(method) to find whether the socket got closed or not??
> Thanks,
> Srini
>
> * * * Best Jokes, Best Friends, Best Food and more. Go tohttp://in.promos.yahoo.com/groups/bestofyahoo/



That's slightly difficult to answer without knowing any context. Do
you want to know if the other end has closed the connection?
Assuming that's the case and you're just using the standard socket
library, it's largely the same as it would be should you do it in C.
A TCP socket with a closed peer will select as 'ready' for read. When
you attempt to read that socket, you'll have a 0 length return.

If you attempt to write to a socket that's been closed by the other
end, you ought to receive a "Broken pipe' socket error. If you
attempt to write to a socket that *you've* already closed, then you
should just get a standard 'Bad file descriptor' socket.error.

Google's your friend with topics like this. There's a lot out there
pertaining to the standard POSIX socket calls.


All times are GMT. The time now is 11:54 PM.

Powered by vBulletin®. Copyright ©2000 - 2014, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.