On 11-Nov-99 Vali Dragnuta wrote:
> What is this all about:
> We're clear that a full TCP implementation would be expensive.
> Because IP is quite stuffy (quite many options to care about), and
> TCP is even more complex for a 8086 toy.TCP is good for long distance
> conections over the internet,but our elks will not need such long
> distance connections ever.
No, IP is more ingenious than you think. You can scale it both up and down.
If you skip all fancy IP options, it's very simple and doesn't take much
memory at all. IP/ICMP/UDP can be done in 1-2 kb (I have done it before).
Even TCP can be much simplified, eg you can set window size to 1, and thereby
disabling all window handling.
> So why do not we set up our OWN PROTOCOL to use it to connect to our
> server ? Thiss protocol (let's name it KISS TCP) would do for
> local network connections.
Once upon a time, I had the same idea (for a different project), but when
I studied my own protocol and IP, I realized that all I wanted was already
there in IP.
> The simplest way to do that is having such a simple multichannel
> protocol running over a serial line to a bigger machine (a real
> Linux) with a multiport board ((with a port for each node))
For a serial network connection, the most easy way is SLIP. SLIP can even be
multipoint, so you can use it as a real LAN.
--
Stefan Pettersson Voice +46-70-5933800 Kanard AB
[EMAIL PROTECTED] ([EMAIL PROTECTED]) Fax +46-221-50180 Vretberga
finger [EMAIL PROTECTED] for my public key S-732 96 ARBOGA
"What a scary world it must be, for those with no UID:GID" /OZ9ABN
