Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!NUSVM.BITNET!ISSKO From: ISSKO@NUSVM.BITNET (Kace Ong) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: Question: TCP/IP implementation for OS/2 Message-ID: <8905200746.aa01845@louie.udel.edu> Date: 24 May 89 13:04:08 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 21 X-Unparsable-Date: Sat, 20 May 89 19:19:04 SST From this net we have come to know that many groups of people are indeed porting (or have ported) pcip to os/2. Some, like myself, are doing it because we need a piece of working code to fill our own urgent needs. Others, like FTP and Microsoft/HP, are developing products to sell to others. Given a choice I'm sure we'll all rather buy a supported, debugged program than to have to roll our own but at this moment there is no product available. I think one reason why there has been an uncommonly long delay in the port is because we all want this version to be "right", i.e. not to repeat the same mistakes of the DOS version. The OS/2 port should have these features: (1) separates the network drivers from the tcp codes, (2) uses OS/2 threads to support tcp tasks, (3) provides DLL call bindings for application in a logical way a la Unix (sockets? streams?) (4) provides applications -- telnet, ftp -- that works with OS/2 VIO,KBD calls. In addition, a commercial offering may also have to provide Netbios and Named Pipes over Tcp/ip. ----------------------------------- Kace Ong Inst of Systems Science ISSKO@NUSVM Singapore -----------------------------------