Jeff,
To supplement Ulrich's answer a little:
(For me at least) One virtual machine. Arguably a leaner memory and disk usage.What advantage would Tomcat-in-Phoenix have over Tomcat on it's own? The contract with the user is still the servlet API, no?
Phoenix hosted apps could, ultimately do all server tasks, that we might normally use Linux for.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!).
We could, in time, have a Phoenix HTTP firewall, delegating internally (without sockets) to a Phoenix loadbalancer, possibly delegaing in-Phoenix again to a Phoenix WebServer. That webserver serverapp hosts sites and Webapps OR delegates internally again to other phoenix server apps (like JAMES or FtpServer) without using the Servlet API.
If we get Catalina working fully inside Phoenix then, in direct answer to your quandry, we could have it listenening on AJP13 as normal. The small trouble is that Catalina is mounted as a kludge at the moment.
Regards,
- Paul H
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
