Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!VAX.FTP.COM!jbvb
From: jbvb@VAX.FTP.COM (James Van Bokkelen)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Windows and interrupt driven ethernet communications (TCP/IP)
Message-ID: <8804142028.AA01064@vax.ftp.com>
Date: 14 Apr 88 20:28:37 GMT
References: <18261@watmath.waterloo.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 12

Making the TCP/IP event-driven (packet interrupts and clock ticks) is
the first required step.  Making it sharable between multiple programs
is also useful.  These are two of the reasons we moved the TCP/IP into
a separate terminate & stay resident module for our 2.0 release.

If you're starting with something like PC/IP, you've got a lot of work to
do, because it makes the basic assumption that the tasker is always running.
Windows doesn't time-slice unless the application participates in its
message-passing paradigm, so a standard application gets stopped dead when
another window becomes active.

James VanBokkelen
FTP Software Inc.