On Jun 2, 2006, at 12:27 PM, Mladen Turk wrote:
Jim Jagielski wrote:
Web Servers are web servers primarily, focused on
HTTP, compliance, speed and capability. Use the
right tool for the right job :)
Agreed.
If you only need a web server, use a web server.
I think that the question is not
Peter Lin wrote:
I'm gonna say that's quite a bit of myth here. If SSL is important, get a
cheap SSL enabled router. Doing software SSL is waste of CPU power and
impacts the server's stability. Anyone that has a lot of HTTPS traffic
shouldn't be using software SSL in my bias opinion. If you
IMO, if you need to move out of pure Java in your Java Web
Server to get acceptable performance, then why use it in
the first place? Plus, if you are concerned about the
security of Apache (cause it's nasty C) and therefore
want to use a Java Web Server, then using JNI means
you've left that warm
On 6/2/06, Jim Jagielski [EMAIL PROTECTED] wrote:
IMO, if you need to move out of pure Java in your Java Web
Server to get acceptable performance, then why use it in
the first place? Plus, if you are concerned about the
security of Apache (cause it's nasty C) and therefore
want to use a Java Web
Jim Jagielski wrote:
Web Servers are web servers primarily, focused on
HTTP, compliance, speed and capability. Use the
right tool for the right job :)
Agreed.
If you only need a web server, use a web server.
I think that the question is not whether to replace
the web server, but whether the
This issue is discussed endlessly as far as I can see, both camps argue
very well for their case
However, my take from personal experience is that its very handy to
have Apache in front, because it gives you a lot of scope to do little
fixes and tweaks to odd users causing problems without
Hi,
I wondering if it's really so good to use Tomcat behind a real web
server like Apache or IIS.
In my Tomcat 5 book there are two reasons to do it so:
1. Tomcat is not as secure as common web servers, especially if you
want to use CGI and SSI (I don't think I want to)
2. Tomcat is
Hi Tim,
Thanks for your answer. I see your point about Apache more convenient
for hackers, than Tomcat.
About outage message. This is of course a problem running Tomcat as
standalone, but I have the control over WebServer IP through the
firewall, so i just start some Show we're down message
Hi,
thanks for the answer! I am paranoid AND lazy, so I totally see
your point :))
Cheers,
Danny
Gaël Lams wrote:
Also, I'm quite
paranoid and for me the less stuff you installed, the better
- I had some problems with the mod_jk (timeouts)
- we are not serving static content
Regards,
Gaël
As it happens I can't really begin to count the number of times we've
applied hacks at the Apache level to work around code bugs (did I say
bug? I meant feature...). Although to be fair most of these are caused
by users/customers doing odd things outside the spec of the current
code.
We also
--- Ga�l Lams [EMAIL PROTECTED] wrote:
Hi,
I wondering if it's really so good to use Tomcat
behind a real web
server like Apache or IIS.
In my Tomcat 5 book there are two reasons to do it
so:
1. Tomcat is not as secure as common web servers,
especially if you
want
If you are running a big site with multiple servers, you do NOT want
to run
Apache in front of your Tomcats -
All that you do is increase latency, and half your performance. The HTTP
connector in TC 5.x is more than adequate to deal with heavy traffic
loads.
To be honest, I try not to use
I'm gonna say that's quite a bit of myth here. If SSL is important, get a
cheap SSL enabled router. Doing software SSL is waste of CPU power and
impacts the server's stability. Anyone that has a lot of HTTPS traffic
shouldn't be using software SSL in my bias opinion. If you are so desparate
13 matches
Mail list logo
