Jeff Turner wrote: > > What advantage would Tomcat-in-Phoenix have over Tomcat on it's own? The > contract with the user is still the servlet API, no?
No, we get rid of the servlet API this way, we're just using Tomcat's webserver and let it handle the HTTP/request/response stuff and possibly serving static HTML files by itself. My point was that I think if Avalon/Phoenix had a component that does HTTP, then we won't need the servlet API anymore. Two possibilities for this HTTP component would be Tomcat or Jo!. > In most environments I've worked in, people have firewalls blocking > pretty much everything except port 80. IMHO, this accounts in no small > part for the success of SOAP. Apache owns port 80; until Phoenix can > talk AJP13, I can't use it (as much as I'd like to!). An AJP13 component would be fine as well, but it ties you to the servlet API. I'd rather have the webserver inside of Phoenix. The outside Apache (or whatever) webserver can dispatch requests to the Phoenix webserver via HTTP, we don't actually need AJP13 for that. Ulrich -- Ulrich Mayring DENIC eG, Systementwicklung -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
