Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!uxc!uxc.cso.uiuc.edu!m.cs.uiuc.edu!rchen
From: rchen@m.cs.uiuc.edu
Newsgroups: comp.lang.c++
Subject: Re: TCP/IP in C++?
Message-ID: <4800054@m.cs.uiuc.edu>
Date: 13 Feb 89 05:31:00 GMT
References: <4800053@m.cs.uiuc.edu>
Lines: 25
Nf-ID: #R:m.cs.uiuc.edu:4800053:m.cs.uiuc.edu:4800054:000:1326
Nf-From: m.cs.uiuc.edu!rchen    Feb 12 23:31:00 1989


/* Written 10:19 am  Feb 12, 1989 by ekrell@hector.UUCP in comp.lang.c++ */
>>In article <4800053@m.cs.uiuc.edu> rchen@m.cs.uiuc.edu writes:
>>
>>Does anyone have implemented TCP/IP in C++?  After a few weeks of working
>>on building C++ modules for NetBIOS, I would imagine a C++ TCP/IP module
>>would be simply beautiful for our project.  Any help would be appreciated.

>What does TCP/IP in C++ mean? The TCP/IP drivers are part of the kernel
>in BSD systems and are written in C. socket() et. al. are system calls
>and you can call them from a C++ program provided you have the right
>function definitions in your system C++ header files.
>    
>Eduardo Krell                   AT&T Bell Laboratories, Murray Hill, NJ

TCP/IP is not limited to BSD 4.2 UNIX any more.  Many parties are working on
porting it to all kinds of systems, such as IBM/PC networks.  One problem
with porting is that the c implementation of TCP/IP is messy, hard to
understand and modify.  With C++, one can define the network interfaces the
way he likes, i.g. one may have a IP class, UDP class as well as TCP class.
A user program can, in turn, define its own interface to the TCP/IP module,
say instead of socket one can define stream.  It is not that existing c
version of TCP/IP doesn't work, it's just not as neat as it should be.

-Ron Chen