Re: Does Microsoft TCP implementation serialize Clien tEventChainedRec eive?

Thanks Max, I did not read DDK doc carefully and was influenced by
NdisMIndicateReceivePacket.

Bi

-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Wednesday, November 27, 2002 4:37 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Does Microsoft TCP implementation serialize
ClientEventChainedRec eive?

Does Microsoft TCP implementation serialize
ClientEventChainedReceive?>My question is, naturally, does Microsoft
TCP protocol driver serialize the ClientEvent

(Chained)ReceiveXXX to TDI client? If not, are those callbacks
supported for TCP?

Yes. The documentation is a bit vague on this, but says:

“The transport does not call ClientEvent(Chained)Receive while the
client has an outstanding normal receive request or has rejected
previously indicated data for a particular incoming normal receive
until that receive is done. However, a transport that supports
expedited data can call ClientEvent(Chained)Receive(Expedited) in the
process of indicating a normal TSDU if an expedited TSDU comes in from
the remote-node peer.”

The successful socket implementations were relying on fact that
ChainedReceiveEvent is never called in reentrant way.

Max


You are currently subscribed to ntdev as: xxxxx@appstream.com
To unsubscribe send a blank email to %%email.unsub%%