RE: Does Apache worth it? Security issues make it worth it
David, Thanks for the enlightening survey. Eitan -Original Message- From: David Wall [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 5:56 PM To: [EMAIL PROTECTED] Subject: Re: Does Apache worth it? Security issues make it worth it One thing architecturally and security-wise about having Apache front Tomcat should also be mentioned. Apache provides native code for serving up HTTP 1.1 (is Tomcat at 1.1 yet, or still 1.0?) which means images and such are transferred much more efficiently. This is also particularly true for SSL code. But the separation makes it easier to put the application server on a box that is not directly connected to the Internet. Architecturally speaking, this is a huge advantage since you don't generally want your application code to be so vulnerable to attacks. Using mod_jk, you can put Tomcat on a private network with a firewall that limits access very tightly -- only allowing connections FROM the web server using the 8007/8009 ports (if that's what you use). This is much more restrictive than needing to allow ports 80/443 from ANY computer in the world. It also means that a hacker has to get through two layers of your system before they can reach the gold, such as modifying JSP pages for graffiti or getting to your database. David
AGAIN: Does Apache worth it?
Hello all, I'm sending this question again, since my mail system crashed and I didn't get any of your answers ( if any ). If you already posted any idea concerning this issue to this mailing list, I will appreciate if you will post it again. Here is the original message: We are intending to use Apache Tomcat as web server in our product, and preliminary experiments show excellent performance. Most of our web pages are JSPs and servlets, and few HTMLs and Gifs. We wonder what is the contribution of Apache in our scenario - some of us think that Tomcat standalone is enough. Is there any advantage of using Apache and not Tomcat standalone? We will appreciate any contributing input. Thanks, - Eitan Ben-Noach Proficiency, Ltd. Tel: +972.2.548.0287 Fax: +972.2.586.3871 email: [EMAIL PROTECTED] The Intelligence in Engineering Supply Chain Collaboration http://www.proficiency.com/
RE: AGAIN: Does Apache worth it?
We have a similar situation. Our product is almost completly JSP's with about 6 html pages. We have found that the web server included with tomcat was just too slow and we get much better performance with the Apache/Tomcat setup. Just my 2 cents worth. Todd -Original Message- From: Eitan Ben Noach [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 10:59 AM To: '[EMAIL PROTECTED]' Subject: AGAIN: Does Apache worth it? Hello all, I'm sending this question again, since my mail system crashed and I didn't get any of your answers ( if any ). If you already posted any idea concerning this issue to this mailing list, I will appreciate if you will post it again. Here is the original message: We are intending to use Apache Tomcat as web server in our product, and preliminary experiments show excellent performance. Most of our web pages are JSPs and servlets, and few HTMLs and Gifs. We wonder what is the contribution of Apache in our scenario - some of us think that Tomcat standalone is enough. Is there any advantage of using Apache and not Tomcat standalone? We will appreciate any contributing input. Thanks, - Eitan Ben-Noach Proficiency, Ltd. Tel: +972.2.548.0287 Fax: +972.2.586.3871 email: [EMAIL PROTECTED] The Intelligence in Engineering Supply Chain Collaboration http://www.proficiency.com/
RE: AGAIN: Does Apache worth it?
Hi Todd, Can you please give me some feeling concerning the performance improvement? Hoe much faster is Apache then Tomcat? What about the number of concurrent users? Is this an issue? Did you find any differences concerning the stability? Thanks, Eitan -Original Message- From: Todd Sussman [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 11:05 AM To: [EMAIL PROTECTED] Subject: RE: AGAIN: Does Apache worth it? We have a similar situation. Our product is almost completly JSP's with about 6 html pages. We have found that the web server included with tomcat was just too slow and we get much better performance with the Apache/Tomcat setup. Just my 2 cents worth. Todd -Original Message- From: Eitan Ben Noach [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 10:59 AM To: '[EMAIL PROTECTED]' Subject: AGAIN: Does Apache worth it? Hello all, I'm sending this question again, since my mail system crashed and I didn't get any of your answers ( if any ). If you already posted any idea concerning this issue to this mailing list, I will appreciate if you will post it again. Here is the original message: We are intending to use Apache Tomcat as web server in our product, and preliminary experiments show excellent performance. Most of our web pages are JSPs and servlets, and few HTMLs and Gifs. We wonder what is the contribution of Apache in our scenario - some of us think that Tomcat standalone is enough. Is there any advantage of using Apache and not Tomcat standalone? We will appreciate any contributing input. Thanks, - Eitan Ben-Noach Proficiency, Ltd. Tel: +972.2.548.0287 Fax: +972.2.586.3871 email: [EMAIL PROTECTED] The Intelligence in Engineering Supply Chain Collaboration http://www.proficiency.com/
Re: AGAIN: Does Apache worth it?
I find Apache with Tomcat to feel noticeably faster. I have no pure HTML pages at all, just JSPs calling backend classes. This is simply due to the fact that Apache serves images faster, i would think. Since my pages contain, on average at least 5 static GIFs/JPGs, this is a lot fewer requests for tomcat to process. I recommend Apache/Tomcat integration for any production setup, though standalone tomcat will perform just fine during the development process. Also, if you have missed traffic on the list, why not check the archives on jakarta.apache.org instead of reposting? -Pete Hi Todd, Can you please give me some feeling concerning the performance improvement? Hoe much faster is Apache then Tomcat? What about the number of concurrent users? Is this an issue? Did you find any differences concerning the stability? Thanks, Eitan -Original Message- From: Todd Sussman [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 11:05 AM To: [EMAIL PROTECTED] Subject: RE: AGAIN: Does Apache worth it? We have a similar situation. Our product is almost completly JSP's with about 6 html pages. We have found that the web server included with tomcat was just too slow and we get much better performance with the Apache/Tomcat setup. Just my 2 cents worth. Todd -Original Message- From: Eitan Ben Noach [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 10:59 AM To: '[EMAIL PROTECTED]' Subject: AGAIN: Does Apache worth it? Hello all, I'm sending this question again, since my mail system crashed and I didn't get any of your answers ( if any ). If you already posted any idea concerning this issue to this mailing list, I will appreciate if you will post it again. Here is the original message: We are intending to use Apache Tomcat as web server in our product, and preliminary experiments show excellent performance. Most of our web pages are JSPs and servlets, and few HTMLs and Gifs. We wonder what is the contribution of Apache in our scenario - some of us think that Tomcat standalone is enough. Is there any advantage of using Apache and not Tomcat standalone? We will appreciate any contributing input. Thanks, - Eitan Ben-Noach Proficiency, Ltd. Tel: +972.2.548.0287 Fax: +972.2.586.3871 email: [EMAIL PROTECTED] The Intelligence in Engineering Supply Chain Collaboration http://www.proficiency.com/
RE: AGAIN: Does Apache worth it?
Pete is correct. We could see the difference when running Tomcat and Apache instead of Tomcat as a stand alone. We only average 25 concurrent users and Tomcat could have been okay, but why settle for okay? Our HTML pages are fairly large due to intense graphics, this is why we use Apache. On a side note we run on a Windows 2000 Server, and have found Apache to be quicker than IIS 5.0 as well. Todd -Original Message- From: pete [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 12:10 PM To: [EMAIL PROTECTED] Subject: Re: AGAIN: Does Apache worth it? I find Apache with Tomcat to feel noticeably faster. I have no pure HTML pages at all, just JSPs calling backend classes. This is simply due to the fact that Apache serves images faster, i would think. Since my pages contain, on average at least 5 static GIFs/JPGs, this is a lot fewer requests for tomcat to process. I recommend Apache/Tomcat integration for any production setup, though standalone tomcat will perform just fine during the development process. Also, if you have missed traffic on the list, why not check the archives on jakarta.apache.org instead of reposting? -Pete Hi Todd, Can you please give me some feeling concerning the performance improvement? Hoe much faster is Apache then Tomcat? What about the number of concurrent users? Is this an issue? Did you find any differences concerning the stability? Thanks, Eitan -Original Message- From: Todd Sussman [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 11:05 AM To: [EMAIL PROTECTED] Subject: RE: AGAIN: Does Apache worth it? We have a similar situation. Our product is almost completly JSP's with about 6 html pages. We have found that the web server included with tomcat was just too slow and we get much better performance with the Apache/Tomcat setup. Just my 2 cents worth. Todd -Original Message- From: Eitan Ben Noach [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 10:59 AM To: '[EMAIL PROTECTED]' Subject: AGAIN: Does Apache worth it? Hello all, I'm sending this question again, since my mail system crashed and I didn't get any of your answers ( if any ). If you already posted any idea concerning this issue to this mailing list, I will appreciate if you will post it again. Here is the original message: We are intending to use Apache Tomcat as web server in our product, and preliminary experiments show excellent performance. Most of our web pages are JSPs and servlets, and few HTMLs and Gifs. We wonder what is the contribution of Apache in our scenario - some of us think that Tomcat standalone is enough. Is there any advantage of using Apache and not Tomcat standalone? We will appreciate any contributing input. Thanks, - Eitan Ben-Noach Proficiency, Ltd. Tel: +972.2.548.0287 Fax: +972.2.586.3871 email: [EMAIL PROTECTED] The Intelligence in Engineering Supply Chain Collaboration http://www.proficiency.com/
Re: Does Apache worth it? Security issues make it worth it
One thing architecturally and security-wise about having Apache front Tomcat should also be mentioned. Apache provides native code for serving up HTTP 1.1 (is Tomcat at 1.1 yet, or still 1.0?) which means images and such are transferred much more efficiently. This is also particularly true for SSL code. But the separation makes it easier to put the application server on a box that is not directly connected to the Internet. Architecturally speaking, this is a huge advantage since you don't generally want your application code to be so vulnerable to attacks. Using mod_jk, you can put Tomcat on a private network with a firewall that limits access very tightly -- only allowing connections FROM the web server using the 8007/8009 ports (if that's what you use). This is much more restrictive than needing to allow ports 80/443 from ANY computer in the world. It also means that a hacker has to get through two layers of your system before they can reach the gold, such as modifying JSP pages for graffiti or getting to your database. David
Re: AGAIN: Does Apache worth it?
Couldn't say when it gets updated, since i subscribed to the list i don't have much need to go there any more :) -Pete Thanks Pete, Does the archive is updated every day? Eitan -Original Message- From: pete [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 12:10 PM To: [EMAIL PROTECTED] Subject: Re: AGAIN: Does Apache worth it? I find Apache with Tomcat to feel noticeably faster. I have no pure HTML pages at all, just JSPs calling backend classes. This is simply due to the fact that Apache serves images faster, i would think. Since my pages contain, on average at least 5 static GIFs/JPGs, this is a lot fewer requests for tomcat to process. I recommend Apache/Tomcat integration for any production setup, though standalone tomcat will perform just fine during the development process. Also, if you have missed traffic on the list, why not check the archives on jakarta.apache.org instead of reposting? -Pete Hi Todd, Can you please give me some feeling concerning the performance improvement? Hoe much faster is Apache then Tomcat? What about the number of concurrent users? Is this an issue? Did you find any differences concerning the stability? Thanks, Eitan -Original Message- From: Todd Sussman [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 11:05 AM To: [EMAIL PROTECTED] Subject: RE: AGAIN: Does Apache worth it? We have a similar situation. Our product is almost completly JSP's with about 6 html pages. We have found that the web server included with tomcat was just too slow and we get much better performance with the Apache/Tomcat setup. Just my 2 cents worth. Todd -Original Message- From: Eitan Ben Noach [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 10:59 AM To: '[EMAIL PROTECTED]' Subject: AGAIN: Does Apache worth it? Hello all, I'm sending this question again, since my mail system crashed and I didn't get any of your answers ( if any ). If you already posted any idea concerning this issue to this mailing list, I will appreciate if you will post it again. Here is the original message: We are intending to use Apache Tomcat as web server in our product, and preliminary experiments show excellent performance. Most of our web pages are JSPs and servlets, and few HTMLs and Gifs. We wonder what is the contribution of Apache in our scenario - some of us think that Tomcat standalone is enough. Is there any advantage of using Apache and not Tomcat standalone? We will appreciate any contributing input. Thanks, - Eitan Ben-Noach Proficiency, Ltd. Tel: +972.2.548.0287 Fax: +972.2.586.3871 email: [EMAIL PROTECTED] The Intelligence in Engineering Supply Chain Collaboration http://www.proficiency.com/
Does Apache worth it?
Hello all, We are intending to use Apache Tomcat as web server in our product, and preliminary experiments show excellent performance. Most of our web pages are JSPs and servlets, and few HTMLs and Gifs. We wonder what is the contribution of Apache in our scenario - some of us think that Tomcat standalone is enough. Is there any advantage of using Apache and not Tomcat standalone? We will appreciate any contributing input. Thanks, - Eitan Ben-Noach Proficiency, Ltd. Tel: +972.2.548.0287 Fax: +972.2.586.3871 email: [EMAIL PROTECTED] The Intelligence in Engineering Supply Chain Collaboration http://www.proficiency.com/
Re: Does Apache worth it?
Hi Eitan, Apache as far as I know is a powerful full blown HTTP server. Tomcat is also a webserver and as you already know it supports servlets and JSP's. The internals of how Tomcat and apache differ I do not know. But from the docs I guess it's the divide and rule policy. Anyting related to static it is directed to Apache since it is a proven and powerful HTTP service and when it is servlets or JSP it is redirected to Tomcat. Basic developement we can use Tomcat I guess for production it is better to use Apache to serve the static files. There is more to it...this is my part. Nive --- Eitan Ben Noach [EMAIL PROTECTED] wrote: Hello all, We are intending to use Apache Tomcat as web server in our product, and preliminary experiments show excellent performance. Most of our web pages are JSPs and servlets, and few HTMLs and Gifs. We wonder what is the contribution of Apache in our scenario - some of us think that Tomcat standalone is enough. Is there any advantage of using Apache and not Tomcat standalone? We will appreciate any contributing input. Thanks, - Eitan Ben-Noach Proficiency, Ltd. Tel: +972.2.548.0287 Fax: +972.2.586.3871 email: [EMAIL PROTECTED] The Intelligence in Engineering Supply Chain Collaboration http://www.proficiency.com/ __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/
Re: Does Apache worth it?
The built in webserver in a Java appserver is really only suitable for testing with - if you are serving more than a few thousand pages per day, or doing anything remotely serious for production use, or your server is on the internet, you should use a real webserver in front of Tomcat, and Apache is the one of choice. Principal reasons are: Performance - Apache is much faster at handling connections and doing basic processing on URLs; it's IO is well optimised (the only thing that beats it is a kernel-space websever like khttpd or Tux) You can also get it to serve any bits of purely static content, such as image files, taking some load off the Java layer. Finally, you can more easily multiplex across multiple Java VM's on multiple boxes, for scalability and redundancy. Configurability - Apache is very powerful and flexible as far as configuration is concerned, and can handle all kinds of complex multi-site hosting issues. Security - Apache has been used on the internet for years by many, many sites, and has withstood all kinds of attacks; most of the vulnerabilities in it have been found and eliminated. By contrast, Tomcat's built in server has not had this level of robust testing. By avoiding the need to connect Tomcat directly to port 80/443, Apache provides an additional layer of insulation between your appserver and the bad guys. Nivedan Nadraj wrote: Hi Eitan, Apache as far as I know is a powerful full blown HTTP server. Tomcat is also a webserver and as you already know it supports servlets and JSP's. The internals of how Tomcat and apache differ I do not know. But from the docs I guess it's the divide and rule policy. Anyting related to static it is directed to Apache since it is a proven and powerful HTTP service and when it is servlets or JSP it is redirected to Tomcat. Basic developement we can use Tomcat I guess for production it is better to use Apache to serve the static files. There is more to it...this is my part. Nive --- Eitan Ben Noach [EMAIL PROTECTED] wrote: Hello all, We are intending to use Apache Tomcat as web server in our product, and preliminary experiments show excellent performance. Most of our web pages are JSPs and servlets, and few HTMLs and Gifs. We wonder what is the contribution of Apache in our scenario - some of us think that Tomcat standalone is enough. Is there any advantage of using Apache and not Tomcat standalone? We will appreciate any contributing input. Thanks, - Eitan Ben-Noach Proficiency, Ltd. Tel: +972.2.548.0287 Fax: +972.2.586.3871 email: [EMAIL PROTECTED] The Intelligence in Engineering Supply Chain Collaboration http://www.proficiency.com/ __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/
Re: Does Apache worth it?
Hi, I am very interested in this issue as well. What if all the pages of the website are generated through servlets and JSP's (except for the token few images/gifs) ? In cases of no static content, would Apache still make any difference ? Thanks. Ben - Original Message - From: David Crooke [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, July 01, 2001 12:39 PM Subject: Re: Does Apache worth it? The built in webserver in a Java appserver is really only suitable for testing with - if you are serving more than a few thousand pages per day, or doing anything remotely serious for production use, or your server is on the internet, you should use a real webserver in front of Tomcat, and Apache is the one of choice. Principal reasons are: Performance - Apache is much faster at handling connections and doing basic processing on URLs; it's IO is well optimised (the only thing that beats it is a kernel-space websever like khttpd or Tux) You can also get it to serve any bits of purely static content, such as image files, taking some load off the Java layer. Finally, you can more easily multiplex across multiple Java VM's on multiple boxes, for scalability and redundancy. Configurability - Apache is very powerful and flexible as far as configuration is concerned, and can handle all kinds of complex multi-site hosting issues. Security - Apache has been used on the internet for years by many, many sites, and has withstood all kinds of attacks; most of the vulnerabilities in it have been found and eliminated. By contrast, Tomcat's built in server has not had this level of robust testing. By avoiding the need to connect Tomcat directly to port 80/443, Apache provides an additional layer of insulation between your appserver and the bad guys. Nivedan Nadraj wrote: Hi Eitan, Apache as far as I know is a powerful full blown HTTP server. Tomcat is also a webserver and as you already know it supports servlets and JSP's. The internals of how Tomcat and apache differ I do not know. But from the docs I guess it's the divide and rule policy. Anyting related to static it is directed to Apache since it is a proven and powerful HTTP service and when it is servlets or JSP it is redirected to Tomcat. Basic developement we can use Tomcat I guess for production it is better to use Apache to serve the static files. There is more to it...this is my part. Nive --- Eitan Ben Noach [EMAIL PROTECTED] wrote: Hello all, We are intending to use Apache Tomcat as web server in our product, and preliminary experiments show excellent performance. Most of our web pages are JSPs and servlets, and few HTMLs and Gifs. We wonder what is the contribution of Apache in our scenario - some of us think that Tomcat standalone is enough. Is there any advantage of using Apache and not Tomcat standalone? We will appreciate any contributing input. Thanks, - Eitan Ben-Noach Proficiency, Ltd. Tel: +972.2.548.0287 Fax: +972.2.586.3871 email: [EMAIL PROTECTED] The Intelligence in Engineering Supply Chain Collaboration http://www.proficiency.com/ __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/
Re: Does Apache worth it?
Eitan, I've done some amount of testing on the Tomcat webserver and the Apache-Tomcat combination and have found the 8080 Tomcat webserver lacking for real production strength deployment. It is excellent for development but speed-wise, feature-wise Apache is a far stronger offering and fronting your Tomcat engine with an Apache engine will yield good results. Vinay - Original Message - From: Eitan Ben Noach [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, July 01, 2001 2:32 PM Subject: Does Apache worth it? Hello all, We are intending to use Apache Tomcat as web server in our product, and preliminary experiments show excellent performance. Most of our web pages are JSPs and servlets, and few HTMLs and Gifs. We wonder what is the contribution of Apache in our scenario - some of us think that Tomcat standalone is enough. Is there any advantage of using Apache and not Tomcat standalone? We will appreciate any contributing input. Thanks, - Eitan Ben-Noach Proficiency, Ltd. Tel: +972.2.548.0287 Fax: +972.2.586.3871 email: [EMAIL PROTECTED] The Intelligence in Engineering Supply Chain Collaboration http://www.proficiency.com/
RE: Does Apache worth it?
Images... -Original Message- From: Benjamin Wong [mailto:[EMAIL PROTECTED]] Sent: Sunday, July 01, 2001 1:01 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Does Apache worth it? Hi, I am very interested in this issue as well. What if all the pages of the website are generated through servlets and JSP's (except for the token few images/gifs) ? In cases of no static content, would Apache still make any difference ? Thanks. Ben - Original Message - From: David Crooke [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, July 01, 2001 12:39 PM Subject: Re: Does Apache worth it? The built in webserver in a Java appserver is really only suitable for testing with - if you are serving more than a few thousand pages per day, or doing anything remotely serious for production use, or your server is on the internet, you should use a real webserver in front of Tomcat, and Apache is the one of choice. Principal reasons are: Performance - Apache is much faster at handling connections and doing basic processing on URLs; it's IO is well optimised (the only thing that beats it is a kernel-space websever like khttpd or Tux) You can also get it to serve any bits of purely static content, such as image files, taking some load off the Java layer. Finally, you can more easily multiplex across multiple Java VM's on multiple boxes, for scalability and redundancy. Configurability - Apache is very powerful and flexible as far as configuration is concerned, and can handle all kinds of complex multi-site hosting issues. Security - Apache has been used on the internet for years by many, many sites, and has withstood all kinds of attacks; most of the vulnerabilities in it have been found and eliminated. By contrast, Tomcat's built in server has not had this level of robust testing. By avoiding the need to connect Tomcat directly to port 80/443, Apache provides an additional layer of insulation between your appserver and the bad guys. Nivedan Nadraj wrote: Hi Eitan, Apache as far as I know is a powerful full blown HTTP server. Tomcat is also a webserver and as you already know it supports servlets and JSP's. The internals of how Tomcat and apache differ I do not know. But from the docs I guess it's the divide and rule policy. Anyting related to static it is directed to Apache since it is a proven and powerful HTTP service and when it is servlets or JSP it is redirected to Tomcat. Basic developement we can use Tomcat I guess for production it is better to use Apache to serve the static files. There is more to it...this is my part. Nive --- Eitan Ben Noach [EMAIL PROTECTED] wrote: Hello all, We are intending to use Apache Tomcat as web server in our product, and preliminary experiments show excellent performance. Most of our web pages are JSPs and servlets, and few HTMLs and Gifs. We wonder what is the contribution of Apache in our scenario - some of us think that Tomcat standalone is enough. Is there any advantage of using Apache and not Tomcat standalone? We will appreciate any contributing input. Thanks, - Eitan Ben-Noach Proficiency, Ltd. Tel: +972.2.548.0287 Fax: +972.2.586.3871 email: [EMAIL PROTECTED] The Intelligence in Engineering Supply Chain Collaboration http://www.proficiency.com/ __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/
RE: Does Apache worth it?
I am very interested in this issue as well. What if all the pages of the website are generated through servlets and JSP's (except for the token few images/gifs) ? In cases of no static content, would Apache still make any difference ? No. Since what will essentially happen is a brokerage call to Tomcat and the response gets redirected through Apache. That's the main point(IMHO) of implementing Tomcat with its' own webserver. So, in the case in which you have nothing but servlet/jsp content you do not need an extra step. --- Michael Wentzel Software Developer Software As We Think - http://www.aswethink.com
Re: Does Apache worth it?
Eitan, it all depends on how ur application works. if u do not have too many static pages not too much of load then Tomcat as a stand-alone is fine. but if u also think of scalability then u must use Apache-tomcat combination as Apache is very robust. Personally i think the effort in gettting Apache-Tomcat combination to work is very much worth. the entire application will be very robust. hope this help, Parminder. On Sun, 1 Jul 2001, Eitan Ben Noach wrote: Date: Sun, 1 Jul 2001 15:32:12 +0200 To: [EMAIL PROTECTED] From: Eitan Ben Noach [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Subject: Does Apache worth it? Hello all, We are intending to use Apache Tomcat as web server in our product, and preliminary experiments show excellent performance. Most of our web pages are JSPs and servlets, and few HTMLs and Gifs. We wonder what is the contribution of Apache in our scenario - some of us think that Tomcat standalone is enough. Is there any advantage of using Apache and not Tomcat standalone? We will appreciate any contributing input. Thanks, - Eitan Ben-Noach Proficiency, Ltd. Tel: +972.2.548.0287 Fax: +972.2.586.3871 email: [EMAIL PROTECTED] The Intelligence in Engineering Supply Chain Collaboration http://www.proficiency.com/
