That isn't happening. All we have is one TCP connection and one small
program exporting file service.
I see. But then, is it the "small program exporting file service" that does
the multiplexing? I mean, if two machines import a gateway's /net and both
run HTTP servers binding to and listening on *:80 what takes care of which
packet belongs to which HTTP server?
On a UNIX clone, or on Windows, because there is exactly one TCP/IP
protocol stack in usual setups no two programs can bind to the same port at
the same time. I thought Plan 9's approach eliminated that by keeping a
distinct instance of the stack for each imported /net.
--On Sunday, November 16, 2008 11:46 AM -0800 Micah Stetson
<[EMAIL PROTECTED]> wrote:
Very well said. This posting summarizes what's been going on:
Thank you.
2. Generality costs.
Not always, and I think you may be overestimating the costs here.
Your later posts talk about making a complete copy of the TCP stack.
That isn't happening. All we have is one TCP connection and one small
program exporting file service.
Micah
