httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <>
Subject Re: project plan
Date Fri, 12 Jul 1996 17:24:45 GMT
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  << >>   |   "There is a time for laughing,
  **  jaguNET Access Services  **      |    and a time for not laughing,
      Email:          |    and this is not one of them"
++         +++      Voice/Fax: 410-931-3157       ++

View raw message