Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!TRWIND.IND.TRW.COM!karl
From: karl@TRWIND.IND.TRW.COM (Karl Auerbach)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: An attempt to rekindle interface discuissions...
Message-ID: <8803040730.AA11717@trwind.ind.TRW.COM>
Date: 4 Mar 88 07:30:46 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 22

How much recursion do you allow within the asynchronous part of the
lower level service interface?  It seems important that the
context of an asynch handler be rich enough to let me do sends/closes/
aborts/etc.

When defining the asynchronous service do you define how much stack
space is available (or does the user have to set his own stack?)
What about register saving/restoreing -- who is responsible?  And is the
user allowd to open up interrupts (assuming they were disabled.)  And
how much base OS function is permitted in the asynch handler (e.g.
can I open a file, muck around in it for a while [long enough that
other net packets have probably arrived]?)

After having worked with various forms of asynch handlers, I find these
less interesting issues to be where the implementation problems occur.

By-the-way, I think this discussion of interfaces is important.
Thanks to those of you who are trying to get the ball rolling again.

More by-the-way, is the goal a binary interface or a source code
interface?  (I prefer the former.)

				--karl--  (Karl Auerbach)