Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ucbcad!ucbvax!cayman.UUCP!brad
From: brad@cayman.UUCP (Brad Parker)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: non-blocking sends in CMU-PCIP
Message-ID: <8711161317.AA11710@cayman.Cayman>
Date: Mon, 16-Nov-87 08:17:51 EST
Article-I.D.: cayman.8711161317.AA11710
Posted: Mon Nov 16 08:17:51 1987
Date-Received: Wed, 18-Nov-87 05:47:13 EST
References: <285884.871114.PAP4@AI.AI.MIT.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 28


I'm new to this group, so please forgive any bogosities... (or is that
"bozosities"? ;=)

I've been reading the mail back and forth about a "standard" interface to
tcp/ip under ms-dos. Coming from the macintosh side of things, I'd be 
interested in people's reactions to a mac-style solution.

Driver I/O on the macintosh is handled via "request blocks" which contain
all of the the pertinent information, including pointers to the data
buffers. Requests can be issued either synchronously or asynchronously.
Async requests can specify an "upcall" routine to be called when the
request completes (we call them completion routines). 

It is entirely possible to implement the "Berkeley socket" abstraction
using this "request block" scheme *and* satisfy some the other problems
such as non-blocking i/o. In fact, it's possible to implement a more
general socket scheme which is (or appears to be ?) a superset of the
the Berkeley implementation, allowing one to support more protocols than
just the IP domain (for I fear I hear the call of I-S-O a 'commin).

Not being "very hip" to the ms-dos low-level world, I'm curious if this
type of scheme is possible under ms-dos? (actually, I'm more interested if
it could be done under ms-dos *and* OS/and-here's-the-kitchen-sink-2)

Brad Parker
Cayman Systems
harvard!cayman!brad