2009/3/25 William A. Rowe, Jr. <wr...@rowe-clan.net>: > Mladen Turk wrote: >> >> The problem with mod_proxy and mod_cluster is the >> fact they are targeted for a *single* web server (httpd) > > Which varies from a one off poorly defined protocol how, exactly? > >> They don't have the generic web server API like mod_jk >> does, and all of them doesn't support async behavior. >> There is simply limitation in both AJP13 and Httpd protocol >> that prevents something like that if one wish to >> have both async, secure and persistent connections >> from the web server to the app server. > > HTTP protocol inhibits this how, exactly?
HTTP could be persistant and secure, but certainly not async. It's still a synchronous protocol, a request and a reply some time later. No unsolicited messages from server to client (browser) for example. BTW, mod_jk / ajp were designed to relay HTTP requests and so are very HTTP 'compliants'. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
