Re: Rought-draft list of things I've seen for 2.0

[Paul Sutton <pa...@ukweb.com>]

On Mon, 28 Apr 1997, Rodent of Unusual Size wrote:
>     Just FWIW, I've recorded some of the for-2.0 issues and ideas at
> 
>      <http://Apache.Golux.Com:9000/Apache200-wishlist>
> 
>     It's not complete - I'm still including some of the suspended PRs -
>     but maybe it's useful as a start..

Lets not rush into long lists of updates that could be made to 2.0 without
first thinking clearly about the major restructuring needed. The three
things we need to work out carefully before any code starts: 

 *  Threading (and sfio?)
 *  OS abstraction - to allow Windows, OS/2 and Unix from the same code
 *  Stackable modules, more API hooks

These will require *major* code surgery (including an API redesign), so
they have to be done before implementing the dozens of other new features
(or implement them first and release 1.2.1 and re-do later, or something).

//pcs

Re: Rought-draft list of things I've seen for 2.0

[Dean Gaudet <dg...@arctic.org>]

Unless RST releases copyright on his code to the "apache group" then
there's no sense even considering it.  He's withdrawn it from the ftp site
where it used to reside.  Those are very negative points against it.
I've never seen the code, and that's probably true for most of the
newer folk.  If we start threading from scratch we avoid some potential
legal hassles.

It sucks to re-invent the wheel, but it's gonna be necessary for
threading.

Dean

On Fri, 2 May 1997, Alexei Kosut wrote:
> Another question is how we start. From Apache 1.2? From scratch? From
> RST's aborted apache-XX code, which actually implemented threading and
> sfio-like stuff rather well, but was based on Apache 1.1, and whose
> status in terms of whether or not the Apache Group can use it is
> unknown.

Re: Rought-draft list of things I've seen for 2.0

[Alexei Kosut <ak...@nueva.pvt.k12.ca.us>]

On Fri, 2 May 1997, Paul Sutton wrote:

> Lets not rush into long lists of updates that could be made to 2.0 without
> first thinking clearly about the major restructuring needed. The three
> things we need to work out carefully before any code starts: 

I agree here.

>  *  Threading (and sfio?)

I'd make these seperate. They're not really related, except that you
need a thread-safe IO library.

>  *  OS abstraction - to allow Windows, OS/2 and Unix from the same code
>  *  Stackable modules, more API hooks
> 
> These will require *major* code surgery (including an API redesign), so
> they have to be done before implementing the dozens of other new features
> (or implement them first and release 1.2.1 and re-do later, or something).

Yes. I think the best strategy might be to assig a person to direct
each part of the 2.0 redesign; someone who's familiar with the topic
in question.

Another question is how we start. From Apache 1.2? From scratch? From
RST's aborted apache-XX code, which actually implemented threading and
sfio-like stuff rather well, but was based on Apache 1.1, and whose
status in terms of whether or not the Apache Group can use it is
unknown.

-- 
________________________________________________________________________
Alexei Kosut <ak...@nueva.pvt.k12.ca.us>      The Apache HTTP Server
URL: http://www.nueva.pvt.k12.ca.us/~akosut/   http://www.apache.org/