We use tomcat standalone on production - most of our pages are dynamic (95%) and the user load is ~7000 and it has been behaving awesome - we use 4.1.31.
hth, Anoop On 5/11/05, Nikola Milutinovic <[EMAIL PROTECTED]> wrote: > > Praveen KUMAR wrote: > > > Hello, > > > > I am little bit confuse in following decision: > > > > Should be use > > > > 1- Apache (2.0.54) + Tomcat (5.0.28) in production with tomcat > > listener (through Coyote connector) configured with mod_jk (1.2.12) > > with apache > > 2- Or Standalone Tomcat (with their standard apache provided by tomcat) > > > > What would be difference in both the scenarios in terms of performance > > and reliability? > > Scenario 2 is easier to implement, there are fewer things that can break > and less config files to maintain. Scenario 1 gives you a unified > setting of your web space. You just simply know that you have one > front-end, Apache. In that case Apache receives the initial HTTP request > and can handle parts of it. > > The most interesting aspect of such a setup are authentication and > redirection. While Tomcat has some rudimentary aliasing, Apache is > superrior when it comes to URL rewriting, redirections and proxying. On > the field of authentication, Tomcat supports HTTP-Basic, HTTP-Digest and > SSL-based authentication. Apache can add to that SPNEGO (Kerberos5, read > Microsoft Active Directory Service), plus several backend mechs for the > Basic and Digest (LDAP, MySQL, PostgreSQL,...). Tomcat can only benefit > from that. > > My advice to you, if you're learning or experimenting, use Tomcat > StandAlone. If you're thinking production, gather your requrements and > see what fits you best. It could again very well be TC standalone. > > Nix. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks and best regards, Anoop
