httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Laurie <...@algroup.co.uk>
Subject Re: [Proposal] "Relayed" Apache API Project
Date Tue, 01 Feb 2000 22:57:14 GMT
costin@eng.sun.com wrote:
> 
> > > Such "Apache relay protocol" server could be either written in C or with
> > > other languages, depending on the needs (i.e. for relayed servlet
> > > engines, mod_relay + mod_java should become a single protocol adapting
> > > layer that drives the servlet engine request/response generation
> > > facility) and should be able to handle multiple connections at once,
> > > keeping them alive for performance reasons.
> > >
> > > The "Apache Relay Protocol" could be based on existing AJP, or based on
> > > more standard full-duplex protocols such as IIOP or anything else.
> 
> My proposal is to separate the discussion it 2 or 3:
> 
> 1. What API do we want to expose to remote engines ( for example
> sub_request but not pool ).
> 
> 2. What wire protocol should we use ( message format and encoding, CDR or
> XDR or AJP or something else ?)
> 
> 2 or 3. What communication mechanism - TCP is a clear one, but we want to
> support unix pipes or shared memory or doors.
> 
> It is not very difficult to make it modular - and probably the best way to
> start would be to re-use some existing code and then invent new protocols.
> 
> I think the API is the most difficult and important part, it's a big
> difference between local calls and IPC ( we must expose non-trivial
> calls, etc).

But isn't that the huge attraction of CORBA? I define the API and the
wire is handled for me? Also, I get cross-language compatibility, as
well as cross-platform.

Cheers,

Ben.

--
SECURE HOSTING AT THE BUNKER! http://www.thebunker.net/hosting.htm

http://www.apache-ssl.org/ben.html

Y19100 no-prize winner!
http://www.ntk.net/index.cgi?back=2000/now0121.txt

Mime
View raw message