Hi,
Thanks for the information.
I have done some testing with Glassfish and found it to be super
simple. My only concern was the memory footprint, which I guess is a
trade off with being feature rich. I have not tried V3 yet, do you
know if this version has a lower memory footprint?
Regards
Matthew Winter
On 22/06/2009, at 1:36 AM, Frederic Jean wrote:
> Hi Matthew,
>
> I think that you are on the right path with having a static HTTP
> server fronting your application servers. Both Apache and nginx will
> do a great job of serving the static content and load balancing
> between the servlet container running your applications. The servlet
> containers can certainly serve static content, but they are not as
> effecient as Apache or nginx at doing so. My preference is to
> reserve application severs (whether servlet containers, Mongrels or
> FastCGI processes) to generate dynamic content.
>
> We currently use Apache HTTPD to front our application servers on
> Project Kenai. We are still using Glassfish V2 to run our web
> application (a JRuby on Rails app). It works well enough for us.
>
> I have used nginx to front another Rails application. I prefer the
> nginx configuration file syntax to the Apache HTTPD one.
>
> I hope that this helps.
>
> Fred
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
