Hi!
Can anybody explain this flag of TDI_SEND? MSDN is silent about it.
And can I use this flag? If it’s undocumented it’s possible this flag can be
removed in future.
vlad-ntdev
Why use it at all?
Berkeley sockets do not contain such semantics :-). Also I’m not sure TCPIP will support this flag.
Max
----- Original Message -----
From: “vlad-ntdev”
To: “NT Developers Interest List”
Sent: Tuesday, May 14, 2002 3:16 PM
Subject: [ntdev] undocumented TDI_SEND_AND_DISCONNECT flag
> Hi!
>
> Can anybody explain this flag of TDI_SEND? MSDN is silent about it.
> And can I use this flag? If it’s undocumented it’s possible this flag can be
> removed in future.
>
> vlad-ntdev
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to %%email.unsub%%
>
I think it’s a remnant from the old OSI TP4 stack that knocked around for a
little while. It’s the type of operation that would be useful there, but
most definitely not supported in the IP protocol suite.
Mark.
At 04:38 PM 5/14/2002 +0400, Maxim S. Shatskih wrote:
Why use it at all?
Berkeley sockets do not contain such semantics :-). Also I’m not sure
TCPIP will support this flag.Max
----- Original Message -----
From: “vlad-ntdev”
>To: “NT Developers Interest List”
>Sent: Tuesday, May 14, 2002 3:16 PM
>Subject: [ntdev] undocumented TDI_SEND_AND_DISCONNECT flag
>
>
> > Hi!
> >
> > Can anybody explain this flag of TDI_SEND? MSDN is silent about it.
> > And can I use this flag? If it’s undocumented it’s possible this flag
> can be
> > removed in future.
> >
> > vlad-ntdev
> >
> >
> >
----- Original Message -----
From: “Maxim S. Shatskih”
To: “NT Developers Interest List”
Sent: Tuesday, May 14, 2002 4:38 PM
Subject: [ntdev] Re: undocumented TDI_SEND_AND_DISCONNECT flag
> Why use it at all?
> Berkeley sockets do not contain such semantics :-). Also I’m not sure
TCPIP will support this flag.
>
> Max
It used in transaction TCP (T/TCP). In it the data are in FIN packet. It’s
very good for high performance HTTP servers. Some sockets implementations
contain MSG_EOF flag in send() function.
And very interesting that IIS 5.0 uses this technique. Look at IIS activity
in TDIMON. You’ll see AND_DISCONNECT flag in TDI_SEND. I wondered how can I
use this way in sockets. And looking for some information about it in TDI.
vlad-ntdev
That’s interesting.
What you can do is load up the debug LSP sockets provider and use this to
trace the sockets parameters. Most obviously have a look at the flags
parameter in send(), but also have a look at the various ioctlsocket()
calls to see if there is an undocumented ioctl being used. Then do some
experimentation of your own.
You can find the debug LSP provider in the Platform SDK.
Mark.
At 05:25 PM 5/14/2002 +0400, vlad-ntdev wrote:
----- Original Message -----
From: “Maxim S. Shatskih”
>To: “NT Developers Interest List”
>Sent: Tuesday, May 14, 2002 4:38 PM
>Subject: [ntdev] Re: undocumented TDI_SEND_AND_DISCONNECT flag
>
>
> > Why use it at all?
> > Berkeley sockets do not contain such semantics :-). Also I’m not sure
>TCPIP will support this flag.
> >
> > Max
>
>It used in transaction TCP (T/TCP). In it the data are in FIN packet. It’s
>very good for high performance HTTP servers. Some sockets implementations
>contain MSG_EOF flag in send() function.
>
>And very interesting that IIS 5.0 uses this technique. Look at IIS activity
>in TDIMON. You’ll see AND_DISCONNECT flag in TDI_SEND. I wondered how can I
>use this way in sockets. And looking for some information about it in TDI.
>
>vlad-ntdev
>
>
>
>—
>You are currently subscribed to ntdev as: xxxxx@muttsnuts.com
>To unsubscribe send a blank email to %%email.unsub%%
The TCP protocol can support it by sending FIN in the non-empty packet, but usual implementations do not support it. Sockets also do
not support it.
Max
----- Original Message -----
From: “Mark S. Edwards”
To: “NT Developers Interest List”
Sent: Tuesday, May 14, 2002 5:04 PM
Subject: [ntdev] Re: undocumented TDI_SEND_AND_DISCONNECT flag
> I think it’s a remnant from the old OSI TP4 stack that knocked around for a
> little while. It’s the type of operation that would be useful there, but
> most definitely not supported in the IP protocol suite.
>
> Mark.
>
>
> At 04:38 PM 5/14/2002 +0400, Maxim S. Shatskih wrote:
> >Why use it at all?
> >Berkeley sockets do not contain such semantics :-). Also I’m not sure
> >TCPIP will support this flag.
> >
> > Max
> >
> >----- Original Message -----
> >From: “vlad-ntdev”
> >To: “NT Developers Interest List”
> >Sent: Tuesday, May 14, 2002 3:16 PM
> >Subject: [ntdev] undocumented TDI_SEND_AND_DISCONNECT flag
> >
> >
> > > Hi!
> > >
> > > Can anybody explain this flag of TDI_SEND? MSDN is silent about it.
> > > And can I use this flag? If it’s undocumented it’s possible this flag
> > can be
> > > removed in future.
> > >
> > > vlad-ntdev
> > >
> > >
> > >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to %%email.unsub%%
>
> And very interesting that IIS 5.0 uses this technique. Look at IIS activity
in TDIMON. You’ll see AND_DISCONNECT flag in TDI_SEND. I wondered how can I
use this way in sockets.
TransmitFile can do this (drop the connection after transmit completes).
Good that TCPIP supports this flag.
Max
> You can find the debug LSP provider in the Platform SDK.
Do they have AFD source in it? If not - then it is just not interesting, it will send all socket calls as IOCTLs to AFD.SYS (checked
build of which is available).
Surely _AND_DISCONNECT thing is some innerworkings of AFD, possibly of TransmitFile.
Max