Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 1279 invoked by uid 6000); 27 Apr 1999 21:01:05 -0000 Received: (qmail 1155 invoked from network); 27 Apr 1999 21:01:00 -0000 Received: from fwns2d.raleigh.ibm.com (HELO fwns2.raleigh.ibm.com) (204.146.167.236) by taz.hyperreal.org with SMTP; 27 Apr 1999 21:01:00 -0000 Received: from rtpmail03.raleigh.ibm.com (rtpmail03.raleigh.ibm.com [9.37.172.47]) by fwns2.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id RAA40038 for ; Tue, 27 Apr 1999 17:00:52 -0400 Received: from dosa.raleigh.ibm.com (dosa.raleigh.ibm.com [9.37.54.227]) by rtpmail03.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id RAA25688 for ; Tue, 27 Apr 1999 17:00:55 -0400 Received: by dosa.raleigh.ibm.com (Postfix, from userid 500) id D30AB1EC23; Tue, 27 Apr 1999 17:00:48 -0400 (EDT) Date: Tue, 27 Apr 1999 17:00:48 -0400 From: Manoj Kasichainula To: new-httpd@apache.org Subject: Re: "embeding" apache(-apr) Message-ID: <19990427170048.A278@dosa.raleigh.ibm.com> Mail-Followup-To: new-httpd@apache.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.2i In-Reply-To: ; from costin@tdiinc.com on Mon, Apr 26, 1999 at 09:21:24AM -0700 Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Mon, Apr 26, 1999 at 09:21:24AM -0700, costin@tdiinc.com wrote: > With apache-apr, it is possible to "embed" apache inside an existing > application ( using the 1 process, many threads model ). > > I tried to do that with Java - with SHARED_CORE, I was able to > load and init libhttpd.so, and to init and configure all standard modules. Cool! > My wish - if you can "expose" more internal methods ( as CORE_PRIVATE for > example, or just make them non-static). ( I have a small list of methods > I used ). The hybrid server is a moving target. I hope your code won't rely on too many of the internal details of the server, because it can all potentially change. But first, what functions do you have in mind? > ( another wish - the configuration of most apache modules can be > done easily using an API instead of the current httpd.conf - except > http_core, that read portions of the http.conf file itself instead > of letting the http_conf "feed" it with configurations. > Unfortunately this is a complex change, I have few hopes you want > this kind of change) I think this would be a great change. It would be cool to have pluggable modules that would let us have an XML-based configuration module, a "legacy" configration module that supports the 1.3 syntax as much as possible, an SNMP-enabled config module that would actually return different values back to the server on-the-fly when told to do so, etc. This kind of support (especially the last one) would require some serious work, though. I need to read Harrie's post on the subject now... -- Manoj Kasichainula - manojk@raleigh.ibm.com IBM, Apache Development