@kbabar2001: "Hi,
    One interesting question related to Windows Sockets
Say, i had opened one port called port number 1000, and starts listening on
to that port for connections, the socket number which i get is say 1500, now
when i get the request, i get some other socket number say 1600, but if i
had closed the socket 1500, which is the socket on which my thread was
listening, but still the other thread which had started the communication on
the 1600 socket works very well, i.e. the communication takes place nicely,
i still did not understand how the communication of socket 1600 is live,
when it main socket 1500 is closed.
Thanks & Regards,
Yash"
    @mayevski: "Hello!
You wrote  on Thu, 26 Aug 2004 17:42:30 +0530:
 JK> i.e. the communication takes place nicely, i still did not understand
 JK> how the communication of socket 1600 is live, when it main socket 1500
 JK> is closed.
(while this doesn't relate to security ... )
When you accept the connection, in fact *new* connection and new socket
appear. You close original socket but this doesn't mean that all accepted
connections should close authomatically. In other words, this is how sockets
work. This is by design. You need to keep track of accepted sockets and
close them yourself.
With best regards,
Eugene Mayevski"
    @kbabar2001: "Thanks for the reply,
Basically i just want to confirm that if i close the socket on which the
programe was listening, what will happen to other sockets that are accepted
and has started the communication.
Thanks
John Kd
news:%23BcvQ$<email_address>
<quote>
1500
sockets"
{'source': 'USENET', 'other_information': '{"reply_count": 2, "forum_name": "microsoft.public.platformsdk.security.20140709.mbox"}', 'file': 'data/output/usenet-microsoft.public.parquet'}