dgaudet     98/12/29 14:21:43

  Modified:    .        STATUS
  Log:
  more details on sfio
  
  Revision  Changes    Path
  1.46      +19 -2     apache-2.0/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /home/cvs/apache-2.0/STATUS,v
  retrieving revision 1.45
  retrieving revision 1.46
  diff -u -r1.45 -r1.46
  --- STATUS    1998/12/17 15:14:06     1.45
  +++ STATUS    1998/12/29 22:21:42     1.46
  @@ -1,5 +1,5 @@
   Apache 2.0 STATUS:
  -Last modified at [$Date: 1998/12/17 15:14:06 $]
  +Last modified at [$Date: 1998/12/29 22:21:42 $]
   
   Release:
   
  @@ -152,7 +152,24 @@
           Status: Ken has volunteered.
   
         o sfio
  -        -1: Dean [until it's shown to be thread safe (RST claims it isn't)]
  +        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
  +         made an auto for thread safety
  +       - sfcvt.c has a "static char *Buf"... needs to have similar
  +         change that we did to the cvt foo in apache
  +       - sftmp.c has a few statics... probably best to just lock in here
  +       - sfpopen.c has a couple statics that need initializing once
  +       - sfexit.c needs a few locks
  +       - sfmode.c Sfrsrv pool of buffers needs to be locked
  +
  +     These can just be avoided:
  +       - the Stdio_b interface has a bunch of statics
  +       - the sfdcdos example discipline has a static
  +     
  +     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.
   
         o bstdio
           This was written by Chris Provenzano as part of his implementation
  
  
  

Reply via email to