fielding 99/01/07 14:55:43
Modified: . STATUS
Log:
Add more info on sfio option
Revision Changes Path
1.47 +14 -3 apache-2.0/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/apache-2.0/STATUS,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- STATUS 1998/12/29 22:21:42 1.46
+++ STATUS 1999/01/07 22:55:42 1.47
@@ -1,5 +1,5 @@
Apache 2.0 STATUS:
-Last modified at [$Date: 1998/12/29 22:21:42 $]
+Last modified at [$Date: 1999/01/07 22:55:42 $]
Release:
@@ -151,7 +151,8 @@
Roy, Lars
Status: Ken has volunteered.
- o sfio
+ o sfio_1998 <http://www.research.att.com/sw/tools/sfio/>
+
Dean says it's not threadsafe. Specifically these need
to be fixed:
- sfprints.c has a "static Sfio_t *f" which would need to be
@@ -169,7 +170,17 @@
There could be more... that was just a quick look around. But
the perl folks seem to be using sfio, so they may have already
- looked into the threading issues.
+ looked into the threading issues. Also, the layering only provides
+ for four primitives: read, write, seek, except (an exception
+ mechanism). I kind of like NSPR's approach which has all the
+ socket primitives in the list as well. It's also lacking the
+ timeout parameters, because it wasn't specifically designed to
+ deal with sockets like NSPR was.
+
+ Roy talked to the authors (Glenn Fowler, David Korn, and
+ Kiem-Phong Vo) at AT&T Research when he gave an Apache
+ talk there in October. We might be able to get one of them
+ to participate, or at least get answers to tough questions.
o bstdio
This was written by Chris Provenzano as part of his implementation
