Re: Sending data to local port
From: Stanley Feng \(MSFT\) (sfeng_at_online.microsoft.com)
Date: 03/31/04
- Previous message: Olaf van der Spek: "TCP: non-blocking connect, connect failure and error code?"
- In reply to: Phil Wood: "Re: Sending data to local port"
- Next in thread: Phil Wood: "Re: Sending data to local port"
- Reply: Phil Wood: "Re: Sending data to local port"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 31 Mar 2004 10:54:38 -0800
"Port" is a concept applies to TCP/UDP, so, if you want to send something to
a "port", that has to go throught the network stack - at least the transport
layer. (So, what you've described below is right conceptionally, as to
detailed implementation, the packet may not necessarily need to go all the
way to the bottom of the stack.).
If you really care about performance, there are many other ways to do
Inter-Process Communication (IPC), just look on google/MSDN for this topic.
Thanks.
-- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples (if any) are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm" "Phil Wood" <anonymous@discussions.microsoft.com> wrote in message news:5276AC0C-CF5A-4952-9B95-D75AA6C7E56C@microsoft.com... > Because it says so in section 2.7 of "The Protocols, TCP/IP Illustrated, Volume 1" :) > > Don't know if this is how it works in Win 2000 > > ----- Olaf van der Spek wrote: ----- > > > "Phil Wood" <anonymous@discussions.microsoft.com> schreef in bericht > news:D4B5D457-6AD8-448F-8CF6-C8A740EA7291@microsoft.com... > > Thanks for the input. My understanding is that in most stack > implementations, when data is sent to the loopback interface (or to a host > interface on the machine) the data must first go down through the transport > and network layers of the stack. Having exited the bottom of the network > layer, the loopback driver adds it to the incoming IP queue, and it > gradually makes its way back up through the network layers. The data does > not reach the ethernet. Is this how it works in Windows 2000? If so, is > there a way of bypassing all this so that I can write data directly to a > port without having to go down through the transport and network layers and > back up again? > > Why would 'most stack implementations' do that instead of delivering the > data directly? > > >
- Previous message: Olaf van der Spek: "TCP: non-blocking connect, connect failure and error code?"
- In reply to: Phil Wood: "Re: Sending data to local port"
- Next in thread: Phil Wood: "Re: Sending data to local port"
- Reply: Phil Wood: "Re: Sending data to local port"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|