Date: Wed, 17 Mar 1999 18:28:00 -0500
From: Manoj Kasichainula <manojk@raleigh.ibm.com>
To: new-httpd@apache.org
Subject: Re: NSPR (was Re: cvs commit: apache-apr/pthreads/src/main
 http_main.c)
Message-ID: <19990317182759.A12372@dosa.raleigh.ibm.com>
Mail-Followup-To: new-httpd@apache.org
References: <36DABCD4.7CA88311@raleigh.ibm.com>
 <Pine.BSF.4.05.9903030251390.66837-100000@pez.hyperreal.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/0.96.1i
In-Reply-To: <Pine.BSF.4.05.9903030251390.66837-100000@pez.hyperreal.org>;
 from Brian Behlendorf on Wed, Mar 03, 1999 at 02:53:59AM -0800
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

On Wed, Mar 03, 1999 at 02:53:59AM -0800, Brian Behlendorf wrote:
> Likewise, I'm not concerned about whether we use Dean's NSPR port, or wrap
> the existing stuff in apache-apr around NSPR.  Either way we end up at the
> right place.

The possible use of NSPR brings up some interesting questions. First
of all, NSPR works on a certain subset of platforms, and that subset
is probably smaller than that of Apache 1.3. Is it a problem to drop
those platforms, or do we want to port NSPR to them? How much loss in
portability are we willing to give up?

Also, since (AFAIK) NSPR provides a thread layer (user or system) on
every platform it supports, do we even need to bother with coding for
the case where we don't have threads available? We could just make sure
that we allow for the use of user threads throughout.

-- 
Manoj Kasichainula - manojk@raleigh.ibm.com
IBM Apache Development Team