mjc         98/02/08 02:08:18

  Modified:    .        STATUS
  Log:
  My feelings. Multi-fibre options would be good imho.
  
  Revision  Changes    Path
  1.18      +8 -8      apache-2.0/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /export/home/cvs/apache-2.0/STATUS,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- STATUS    1998/02/07 20:12:45     1.17
  +++ STATUS    1998/02/08 10:08:17     1.18
  @@ -30,7 +30,7 @@
       varies from the above such that if it's shown that the "autoconf
       toolset" can do what we want, with less headache than what we
       have, then we go for it)
  -     Status: Jim +1, Ken +1, Marc +1
  +     Status: Jim +1, Ken +1, Marc +1, MarkC +1
   
     * The "autoconf toolset" should include all three: autoconf, automake, and 
       libtool.
  @@ -44,17 +44,17 @@
       to add more, but try not to duplicate earlier items too much.
   
       * multithreading.  
  -     Status: Brian +1, Ken +1, Dean +1, Jim +1, Paul +1, Sameer +1, Marc +1, 
Ralf +1
  +     Status: Brian +1, Ken +1, Dean +1, Jim +1, Paul +1, Sameer +1, Marc +1, 
Ralf +1, MarkC +1
        - Thread Abstraction
  -       Status: Sameer +1, Marc +1
  +       Status: Sameer +1, Marc +1, MarkC +1
    
       * revamped process model (Dean's proposal)
         Dean says: it's hard to do the multithreading work cleanly without
         considering a bunch of this
  -     Status: Marc +1 on much of it; threads aren't enough for perf.
  +     Status: Marc +1 on much of it; threads aren't enough for perf. MarkC +1
   
       * new layered I/O.
  -     Status: Brian +1, Ken +1, Dean +1, Jim +1, Paul +1, Sameer +1, Marc +1, 
Ralf +1
  +     Status: Brian +1, Ken +1, Dean +1, Jim +1, Paul +1, Sameer +1, Marc +1, 
Ralf +1, MarkC +1
       
         . sfio
        Status: Dean -1 until it's shown to be thread safe (RST claims it isn't)
  @@ -89,14 +89,14 @@
   
         . change API 'phase' model to use module-registered hooks rather
        than a fixed static structure
  -     Status: Ken +1, Ralf +1
  +     Status: Ken +1, Ralf +1, MarkC +1
   
         . clearly identify API functions by renaming them
        Status: Ken +1, Ralf +1
   
         . backward compatibility with 1.3 (just require a recompile)
        if functions get renamed, old names retained as wrappers
  -     Status: Paul +1, Sameer +1, Marc +1, Ralf +1
  +     Status: Paul +1, Sameer +1, Marc +1, Ralf +1, MarkC +1
   
         . make API call syntax rational (e.g., all r*() routines list r
        as their first argument, et cetera)
  @@ -108,7 +108,7 @@
       * rewrite in C++
        . Yes: 
        . doesn't like the idea, but is open to it: Marc +1, Ralf +1
  -     . No way ever:
  +     . No way ever: MarkC +1
   
   
   Closed issues:
  
  
  

Reply via email to