Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Message-ID: <3924C86C.683FEE03@ix.netcom.com>
Date: Thu, 18 May 2000 21:51:56 -0700
From: Sam Talebbeik <saeedt@ix.netcom.com>
MIME-Version: 1.0
To: new-httpd@apache.org
Subject: Re: Lack of support for Apache and Broadvision.
References: <200005182013.aa19384@gremlin-relay.ics.uci.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Roy, thanks for the feedback. I also thought whatever this
Netscape NSAPI module is doing can potentially be done by
porting it to a Apache module written in C. If that is possible then
there is no technical barrier.

How can anyone start the process of porting a proprietary piece of
software from another vendor when there is no agreement between the
vendor and the ASF? Is ASF able to provide support or sanction such an
effort or there is a feeling that this is not worth the effort.

  Regards,
  Sam 


"Roy T. Fielding" wrote:
> 
> Broadvision technology is three years out-of-date on all fronts,
> not just their NSAPI interface.  It would be far easier and more
> robust for them to implement an Apache module than it would be
> for us to implement a mod_nsapi.  NSAPI itself is dog slow and
> hard to replicate without a multithreaded single-process daemon,
> and even if we did replicate it the result would suffer from all
> of the robustness problems of Netscape.
> 
> While you are welcome to try to create a mod_nsapi module that
> acts as a wrapper around NSAPI modules, I think you would be better
> served by more modern application server technologies that are
> based on open frameworks.
> 
> ....Roy