From: Jim Jagielski <jim@jaguNET.com>
Message-Id: <199607121724.NAA07095@shado.jaguNET.com>
Subject: Re: project plan
To: new-httpd@hyperreal.com
Date: Fri, 12 Jul 1996 13:24:45 -0400 (EDT)
In-Reply-To: <199607121703.NAA24838@skydive.ai.mit.edu> from "Robert S. Thau"
 at Jul 12, 96 01:03:49 pm
Content-Type: text
Sender: owner-new-httpd@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com

Robert S. Thau wrote:
> 
>   I'd tend to have to agree with this.  First of all, any features you want
>   for Apache can be held until the server becomes multi-threaded.  It has
> 
> Allow me to show my contrarian streak.  We actually have a fair number
> of things lying around which could be wrapped up in 1.2 --- minimal
> HTTP/1.1 compliance, PUT-handling, revised versions of certain modules,
> etc., which could probably be wrapped up fairly quickly; certainly more
> quickly than the threaded server could be brought to market. 
> 
> So, given all that, what is the good reason not to wrap up the easy bits
> into a 1.2 release while we have 2.0 in the OR under general anesthesia
> in another branch?
> 

I totally agree. Let's add as much as we can to 1.2 and then *wow* 'em
with 2.0.

Getting 2.0 ready for prime-time will take a lot of work, and there's
too much we can add/do/implement with 1.2 to hold out for too long.

-- 
Jim Jagielski  << jim@jaguNET.com >>   |   "There is a time for laughing,
  **  jaguNET Access Services  **      |    and a time for not laughing,
      Email: info@jaguNET.com          |    and this is not one of them"
++    http://www.jaguNET.com/         +++      Voice/Fax: 410-931-3157       ++