From: Dominik Werder <dwerder@...>
Date: 2003-05-17T22:24:34+09:00
Subject: Re: TCP Sockets

> It doesn't need knowledge of the application protocol, but it needs to
> know -all-about TCP/IP -- it needs the headers for every packet --
> source, destination, flags, window, mss, length.

You're right, my example wasn't that good.

I tell you what I wanna do:

I got two application servers with multiple threads each to handle 
requests. A Request on one server could need data from the second server. 
But I don't want to create a new connection each time. So I wanna have one 
steady connection and when one or more threads need data from the other 
server, they can send their packets right through this one connection. Like 
telecommunications networks (ATM?): The packets are mixed together, send 
through the line and extracted on the other end.

But here it is easier, because I don't need to do the routing because the 
connection is already there. Because of this the router example was 
terrible bad :(


> Once you're at the application (socket) level, you have buffers to deal
> with -- you don't know whether the 99 bytes was 1, 2 or 3 packets at
> all, unless you know how big the chunks the sender sends are.

The module I'm trying to do should not need any information of the 
protocols which are used on the line. It should only mix packets together, 
send it, and on the other side, the same module extract the packets again 
:)

bye!
Dominik