Return-Path: Delivered-To: apmail-jakarta-avalon-phoenix-dev-archive@apache.org Received: (qmail 35174 invoked from network); 1 Oct 2002 09:43:03 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 1 Oct 2002 09:43:03 -0000 Received: (qmail 10578 invoked by uid 97); 1 Oct 2002 09:43:58 -0000 Delivered-To: qmlist-jakarta-archive-avalon-phoenix-dev@jakarta.apache.org Received: (qmail 10525 invoked by uid 97); 1 Oct 2002 09:43:57 -0000 Mailing-List: contact avalon-phoenix-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon-Phoenix Developers List" Reply-To: "Avalon-Phoenix Developers List" Delivered-To: mailing list avalon-phoenix-dev@jakarta.apache.org Received: (qmail 10513 invoked by uid 98); 1 Oct 2002 09:43:57 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3D996DBD.2020709@denic.de> Date: Tue, 01 Oct 2002 11:41:17 +0200 From: Ulrich Mayring Organization: DENIC eG User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Avalon-Phoenix Developers List Subject: Re: Phoenix and the Web References: <000001c268b1$6ae35a60$94a85982@LSD> X-MIMETrack: Itemize by SMTP Server on notes/Denic(Release 5.0.10 |March 22, 2002) at 01.10.2002 11:42:50, Serialize by Router on notes/Denic(Release 5.0.10 |March 22, 2002) at 01.10.2002 11:42:51, Serialize complete at 01.10.2002 11:42:51 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; format=flowed X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Leo Simons wrote: > ...I'm not too familiar with ajp. IIRC I didn't like it because it > made too many assumptions and used strings/chars.....but that was > when the world still used JServ....it sounds like the sensible > way too go.... > > I'd like to see it :) The problem I have with this approach is that there seems to be no sensible Java API (similar to the Servlet API) to manipulate incoming requests and outgoing responses. It's not very OO, apparently, but when we bring something into Phoenix, we want it to be OO. > Avalon-based http 1.1 implementation is high on the would-like- > to-see-but-no-itch-to-develop list for I suspect quite a few > people. > > There's quite a few http impls in java available to rip off of course > (one I know of is coyote) Again I have the "missing API" problem here. Suppose we have an HTTP component, then how are we going to use it? We could either implement the whole Servlet API on top of it (yuck) or do something proprietary. Like maybe this: if (uri.equals("/what/ever")) doThis(); else if (uri.equals("/what/else")) doThat(); else doSomethingElse(); It's not the way we want to work in Phoenix :) > 7) probably the coolest is writing an avalon+event-based http > implementation from scratch that beats everything else wrt speed, > architecture, and pluggability. Develop an Avalon-specific API for HTTP thereby blowing the Servlet API out of the water? > 8) roll-your-own protocol and apache httpd module > (one thing I found out recently: modules are easy =) > 9) run java within PHP within apache and have that talk to phoenix > over AltRMI > 10) run java within Python (mod_snake) within apache and have that > talk to phoenix over AltRMI > 11) rip apart axis and run it inside phoenix, then have it > accept calls from IIS.Net > 12) run phoenix inside Jboss and map requests from Jetty to phoenix > through Jboss's JMX kernel (I think it still works that way?) 8-12: Please not :) Ulrich -- Ulrich Mayring DENIC eG, Systementwicklung -- To unsubscribe, e-mail: For additional commands, e-mail: