Hello !
Where can I read about correlation between TDI operations and Sockets functions ?
For example, if an application opens port, what order of TDI-calls will there be ?
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
socket - does not map to TDI.
bind - create an address file object.
connect - create a connection file object and TDI_CONNECT.
listen - set event handler for TDI_EVENT_CONNECT.
accept - implemented in the client, based on TdiEventConnect routine, pre-connected connection file objects for the accepted sockets and TDI_ACCEPT returned from TdiEventConnect. TDI_ACCEPT completion delivers the full-formed accepted socket.
send - TDI_SEND, possibly with additional buffering - TDI_SEND will complete only when all ACKs will arrive, sockets expect other send() semantics.
recv - implemented in the client, based on TdiEvent(Chained)Receive(Expedited) routine and, for some cases, TDI_RECEIVE returned by this event.
closesocket is very complex, since TDI has no lingering close functionality, all must be done in the client (send your TDI_DISCONNECT_RELEASE, wait for remove TdiEvenDisconnect(TDI_DISCONNECT_RELEASE), then close both file objects).
Listen backlog, lingering close and SO_(SND)RCVBUF stuff belongs to the TDI client, TCPIP does not provide this.
Max
----- Original Message -----
From: foxgen
To: NT Developers Interest List
Sent: Monday, February 04, 2002 3:26 PM
Subject: [ntdev] TDI operations
You are currently subscribed to ntdev as: xxxxx@storagecraft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com