Jeff Turner wrote: > > I'd have thought that using Avalon in a servlet environment is *the* > most common usage. With all the IoC in the Servlet API, Avalon seems a > natural fit for writing more complex servlets..
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. 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. 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 :) Ulrich -- Ulrich Mayring DENIC eG, Systementwicklung -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
