Strange behaviour of ClientEventDisconnect

NTDEV
1

If I do:
send request
read some of answer but not all
TDI_DISCONNECT with flags TDI_RELEASE
I never get any ClientEventDisconnect but if I read all available data I do
get ClientEventDisconnect, is this normal behaviour?

Hitta rätt på nätet med MSN Search http://search.msn.se/

2

“Peter Hallberg” wrote in message
news:xxxxx@ntdev…
> If I do:
> send request
> read some of answer but not all
> TDI_DISCONNECT with flags TDI_RELEASE
> I never get any ClientEventDisconnect but if I read all available data I
> do get ClientEventDisconnect, is this normal behaviour?
>
Yes, this is similar to the behavior of sockets when half-closed.

Thomas F. Divine, Windows DDK MVP

3

Yes. Your call to TDI_DISCONNECT_RELEASE sends the TCP FIN, it is like
Berkeley’s shutdown(SD_SEND).

The arriving ClientEventDisconnect(RELEASE) is the arriving FIN, you must
read all of the data to get this.

For the rest, read the TCP RFC.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

----- Original Message -----
From: “Peter Hallberg”
To: “Windows System Software Devs Interest List”
Sent: Tuesday, January 24, 2006 5:50 PM
Subject: [ntdev] Strange behaviour of ClientEventDisconnect

> If I do:
> send request
> read some of answer but not all
> TDI_DISCONNECT with flags TDI_RELEASE
> I never get any ClientEventDisconnect but if I read all available data I do
> get ClientEventDisconnect, is this normal behaviour?
>
> _________________________________________________________________
> Hitta rätt på nätet med MSN Search http://search.msn.se/
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com