> From: keenny [mailto:kee...@start.no]
> I was just wondering if anybody has any opinions
> as to how this
> can be done most effectively (highest throughput, low cpu
> consumption etc).
> Some alternatives being:
>
> lighttpd -> mod_proxy -> tomcat -> application code
Lots of moving parts. There has to be a better solution!
> lighttpd -> fastcgi -> application code
Depends on how the CGI is implemented. Not one for a Tomcat list :-).
> tomcat -> application code
Surprisingly fast, even for static content. Depending on your mix of static
and dynamic content, this may use less CPU than the combination of lighttpd and
mod_proxy as there are fewer moving parts per request.
> asyncweb/mina -> application code
Never used, so don't know!
Do the AJAX requests have to be served from the same port as the static
content, or can they come from a different port? If a different port is
acceptable, you might want to try using lighttpd on port 80 to serve the static
content, and Tomcat or another servlet engine on a different port (8080?) to
serve the AJAX requests. But check the benchmarks on Tomcat before you
introduce two pieces of software into the mix. You might be pleasantly
surprised!
- Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
