Extending 2.0 beyond HTTP ?

[bryan <br...@yahoo.com>]

Hi,

I have been looking at 2.0, and have been hoping to
try out using it for a non-httpd protocol.  As far as
I can understand (which is clearly not much), HTTP is
a fairly basic assumption for 2.0, with a lot of the
protocolese in main/ (which i assume means it's not
really a module).  Is this correct?

I'd imagine that this has been discussed before, so
any pointers to places and subjects to search for are
highly appreciated.

Much thanks,

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: Extending 2.0 beyond HTTP ?

[Manoj Kasichainula <ma...@io.com>]

On Tue, Feb 29, 2000 at 05:37:57PM -0800, bryan wrote:
> I have been looking at 2.0, and have been hoping to
> try out using it for a non-httpd protocol.  As far as
> I can understand (which is clearly not much), HTTP is
> a fairly basic assumption for 2.0, with a lot of the
> protocolese in main/ (which i assume means it's not
> really a module).  Is this correct?

HTTP is still a bit too tied to the core of the server, but in theory,
there shouldn't be anything in the way of adding a new protocol. See
mod_echo for a simple one. We think that a more complicated protocol
should be possible, but we haven't tried yet.

Re: Extending 2.0 beyond HTTP ?

[Bill Stoddard <st...@raleigh.ibm.com>]

> Hi,
>
> I have been looking at 2.0, and have been hoping to
> try out using it for a non-httpd protocol.  As far as
> I can understand (which is clearly not much), HTTP is
> a fairly basic assumption for 2.0,
No, not really, not when compared to Apache 1.3.  All the code to bind a
network request (of any protocol) to a thread of execution is contained in
an MPM module (see src/modules/mpm).  You could easily call a different set
of routines in the MPM to handle any protocol coming in off the network. Or,
you could add a few directives to the MPM to enable you to listen for HTTP
traffic on one port and "protocol X" traffic on another port and handle them
appropriately.  That is pretty much what will be done to add SSL support to
Apache.

Bill

Re: Extending 2.0 beyond HTTP ?

[rb...@apache.org]

Try looking at mod_echo.  Apache 2.0 has two parts, a server framework and
an HTTP implementation.  Mod_echo is a simple echo server which uses the
Apache framework.  We have not documented this aspect of 2.0 much, because
we are focusing on getting it out the door, but it does work, AFAIK.

Ryan

On Tue, 29 Feb 2000, bryan wrote:

> Hi,
> 
> I have been looking at 2.0, and have been hoping to
> try out using it for a non-httpd protocol.  As far as
> I can understand (which is clearly not much), HTTP is
> a fairly basic assumption for 2.0, with a lot of the
> protocolese in main/ (which i assume means it's not
> really a module).  Is this correct?
> 
> I'd imagine that this has been discussed before, so
> any pointers to places and subjects to search for are
> highly appreciated.
> 
> Much thanks,
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 


Come to the first official Apache Software Foundation
Conference!!!   <http://ApacheCon.Com/>

_______________________________________________________________________________
Ryan Bloom                        	rbb@ntrnet.net
2121 Stonehenge Dr. Apt #3
Raleigh, NC 27615		Ryan Bloom -- thinker, adventurer, artist,
				     writer, but mostly, friend.
-------------------------------------------------------------------------------