Re: Socket weirdness
- From: "Dave Sexton" <dave@jwa[remove.this]online.com>
- Date: Tue, 19 Sep 2006 05:11:12 -0400
Interesting. Is there a managed counterpart?
--
Dave Sexton
"Vadym Stetsyak" <vadym_s@xxxxxxx> wrote in message news:%23CegYl72GHA.4484@xxxxxxxxxxxxxxxxxxxxxxx
Hello, William!
WSM> I guess the bit is not set in a send either - only the ACK. So I
WSM> guess that means you must always do at least two sends (at the client)
WSM> before you will notice a shutdown receive at server.
There is an interesting API in the winsock - WSASendDisconnect/WSARecvDisconnect.
The result is virtually the same as with shutdown, but results in one call...
--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com
.
- References:
- Socket weirdness
- From: William Stacey [MVP]
- Re: Socket weirdness
- From: Dave Sexton
- Re: Socket weirdness
- From: William Stacey [MVP]
- Re: Socket weirdness
- From: Dave Sexton
- Re: Socket weirdness
- From: William Stacey [MVP]
- Socket weirdness
- Prev by Date: RE: How to determine when a process has finished initial loading
- Next by Date: Announcement: NLog 1.0 has been released
- Previous by thread: Re: Socket weirdness
- Next by thread: Re: Socket weirdness
- Index(es):