Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Date: Tue, 16 May 2000 12:01:35 -0700 (PDT)
From: Greg Stein <gstein@lyra.org>
To: new-httpd@apache.org
Subject: Re: Embeding apache into an application
In-Reply-To: <39217CC9.F2224CEB@yahoo.com>
Message-ID: <Pine.LNX.4.10.10005161200080.11417-100000@nebula.lyra.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 16 May 2000, cizaire_liste wrote:
> Hello,
> 
> I want to embed apache into an already written application 
> (on solaris, linux and NT), by loading it as a shared library, 
> and that raises some points :
> - how to use apache when my application provides the main
> (maybe something to do with REALMAIN)
> - how to prevent apache to fork (but multi threading is ok)
> (maybe something to do with MULTITHREAD but I am not sure it
> is handled on unix)
> - how to get the http requests
> (maybe something like a mod_... to develop)
> - what is the minimal configuration
> - how to do it well
> 
> I hope that I can have some good advices from you.

Apache is not designed for this at all. It presumes that it has control
over the process, its threads, the main loop, etc.

I'm not sure what the advantage of embedding Apache would be. What are you
actually trying to do? Somehow control the embedded app?

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/