Mail Archives: opendos/2003/12/04/10:11:58
| X-Authentication-Warning:  | delorie.com: mail set sender to opendos-bounces using -f
 | 
| Message-Id:  | <5.1.0.14.0.20031204071135.00a7a940@popj.myexcel.com>
 | 
| X-Mailer:  | QUALCOMM Windows Eudora Version 5.1
 | 
| Date:  | Thu, 04 Dec 2003 07:11:42 -0800
 | 
| To:  | opendos AT delorie DOT com
 | 
| From:  | Bud <caburnham AT myexcel DOT com>
 | 
| Subject:  | Re: Arachne Web browser for DOS
 | 
| Mime-Version:  | 1.0
 | 
| Reply-To:  | opendos AT delorie DOT com
 | 
--=======414185B=======
Content-Type: text/plain; x-avg-checked=avg-ok-49FF3D61; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 8bit
.
.
.
>It does and the answer is no as one can't have two TCP/IP stacks,
>at least not sharing the same IP address.
.
.
.
>If one were to write a TCP/IP client, say FTP, with built-in
>TCP/IP, it couldn't simultaneous share the packet driver with Arachne's
>TCP/IP.  Arachne and an FTP client could on the other hand share
>a TCP/IP stack.  MS didn't define a standard TCP/IP interface for
>DOS as it did with WinSock for Windows.
This is a very interesting conversation.  I am working on porting Arachne 
to the Datalight TCP/IP Stack, SOCKETS.  SOCKETS is a TSR TCP/IP stack and 
has a WINSOCKv2 compatible interface.
What has been said about Arachne utilizing WATTCP and the issues behind 
writing TCP/IP applications with WATTCP are true.
Hopefully, I will be able to post some new news here soon about my progress 
in porting Arachne.
Bud
--=======414185B=======--
- Raw text -