Re: Applying Avalon in a Servlet Environment

[Paul Hammant]

Ulrich,
Strange, I'd have thought THE most common usage of Avalon would be with
Phoenix (blocks and .sar applications and such). Actually what I am
missing in Phoenix is some way to do HTTP - if we had that, then nobody
would want or need to use Avalon in a servlet environment. 

Agree.
To implement
a basic HTTP server would be easy, to integrate a more full-featured one
like Jo! or Tomcat would probably be not quite as easy, but the better
choice in the long run.
Jo! works well.  We'll have to check with Hendrick to see if he moved to 
LogEnabled when we did.
Tomcat works but needs loads of work.
I forked another effort (Acme Web server) to Phoenix some months ago and 
have it under the Avalonia project at sourceforge.  It is a tiny basic 
webserver with marginal servelet support.

Here's what I currently do: my Avalon/Phoenix services can be talked to
over a socket connection and I invented a minimal protocol for that.
Then I use my socket XSP taglib for Cocoon1 to seamlessly integrate
these services into a Cocoon webapp. So I don't actually need to do HTTP
into Phoenix, I just talk over the socket and leave the HTTP
request/response handling to my webserver. Maybe this is less than
ideal, but it's there and it works :)
And also does not break the "Servlet contract" which stipulates nothing 
more than javax.servlet.* visible in the classpath from the underlying 
server.

- Paul H

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>