[usocket-cvs] r121 - in usocket/trunk: doc notes

ehuelsmann at common-lisp.net ehuelsmann at common-lisp.net
Wed Oct 18 16:46:43 UTC 2006


Author: ehuelsmann
Date: Wed Oct 18 12:46:42 2006
New Revision: 121

Removed:
   usocket/trunk/notes/accept-apis.txt
Modified:
   usocket/trunk/doc/design.txt
Log:
Remove cruft accidentally added in r119. This wasn't part of the contribution.

Modified: usocket/trunk/doc/design.txt
==============================================================================
--- usocket/trunk/doc/design.txt	(original)
+++ usocket/trunk/doc/design.txt	Wed Oct 18 12:46:42 2006
@@ -13,7 +13,7 @@
  * Motivation
  * Design goal
  * Functional requirements
- * Comments on the functional requirements
+
 
 
 

@@ -83,33 +83,6 @@
  - OpenMCL
 
 
-The lifetime of a socket can be described with these steps:
-
- 1. Socket creation (socket() function)
- 2. Socket initializaiton (setsockopt(), bind() and listen()/connect() funcs)
- 3. Socket use (accept() / recv[from], send[to])
- 4. Socket termination (shutdown())
- 5. Socket destruction (close())
-
-While for most applications steps 1-3 can be condensed into 1 (which most
-implementations do), if the library wants to be extensible into other
-domains than IP, a means should be provided to do socket initialization
-without knowing what parameters to accept beforehand: other protocols
-require parameters for setsockopt we will not know about in advance.
-
-There are several possibilities to address this issue:
-
- a. Force the 3 steps apart [hard to get done with the current status
-    for some implementations, as they are currently integrated in the
-    public interface].
- b. Find a mechanism to pass options which we want setsockopt to
-    be called with. Problem: what to do with implementations which
-    don't support setting of all options *before* the bind() call?
-    Does it matter that some options may be set after the bind()
-    call? What if they're not set before connect() [buffer size changes
-    have to be set before connect()]?
- c. ... ?
-
 Comments on the design above
 ============================
 



More information about the usocket-cvs mailing list