James Jouett typed the following on 05:00 PM 1/30/2001 -0600
>There are no pages or images - I'm just using HTTP as the mechanism to post a
>request to a servlet from a client, so nothing is static. My main concerns are
>the configuration options of standalone Tomcat (security, SSL, redirection,
>
, January 30, 2001 2:42 PM
To: [EMAIL PROTECTED]
Subject: Re: Do I need apache for servlet-only use?
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
> -Original Message-
> From: James Jouett [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 30, 2001 2:42 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Do I need apache for servlet-only use?
>
> Actually, I am defining the production environment, and the design uses
> servl
t: Tuesday, January 30, 2001 2:42 PM
To: [EMAIL PROTECTED]
Subject: Re: Do I need apache for servlet-only use?
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 p
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:2
-
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 apac
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
standalon
