Actually, I am defining the production environment, and the design uses servlets to
provide
scalability and redirection capabilities. So, if I am using servlets with no static
web pages in my
production envrionment, is there any benefit or added capabilities by using Apache or
will Tomcat
standalone provide all of the flexibility and functionality I need?
Thanks
Cor Ruiten wrote:
> If you are in a development cycle where you only use servlets, then I would suggest
>that you
> utilize Tomcat in standalone mode, as you will not gain anything by throwing Apache
>into the mix.
> In fact,
>
> However, since you will ultimately deploy to a production environment where you will
>most likely
> have a web-server such as Apache, I would suggest that you configure the
>connectivity between
> Apache and Tomcat as part of your testing cycle to ensure that you are testing in an
>environment
> that is as close as possible to the production deployment environment.
>
> Cor
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of James Jouett
> Sent: Tuesday, January 30, 2001 2:22 PM
> To: [EMAIL PROTECTED]
> Subject: Do I need apache for servlet-only use?
>
> The main benefit I've read of using apache with tomcat instead of just
> tomcat standalone is that apache is faster for serving static pages. If
> I am starting a new development effort that will only be using servlets,
> is there any reason to use apache, or should I just stick with tomcat in
> standalone mode to service the requests? Any comments would be
> appreciated.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
