tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Hagger <>
Subject Re: Tomcat as a standalone webserver. Why not?
Date Thu, 01 Jun 2006 14:57:35 GMT
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

We also deal heavily with accesses from mobile phones, each one of which
has new and interesting features in its web browser, some of which just
can't be easily dealt with without direct control over the
request/response headers which Apache makes easy.

But more generally another big win we have found is the ability to
fairly easily have Apache catch certain requests (ie for specific users)
and hand them off to development/staging systems rather than the
production systems.  This is used quite often in our test/release cycle,
and avoids having to have the production system tomcat layer even know
that such hacky stuff is going on, whilst outside users can't
necessarily know which back-end system they are using.


On Thu, 2006-06-01 at 16:30 +0200, Danny Lee wrote:
> Hi!
> Thanks for your answer. I use url-rewrite magic servlet (analog to
> apache mod_rewrite), so I have the same "on the fly" rewrite 
> functionality (the rewrite-rules.xml is checked every minute or somth).
> I do all the request/response stuff in Tomcat as long it's relevant
> and a part of the system I don't want to move a part of functionality
> to Apache, I prefer having "all-in-one" solution (this is why I use
> Quartz for scheduled tasks and not some chron-jobs).
> And I can't see the connection, why my code have to be perfectly bug 
> free? I mean, if I do have bugs Apache wont come and save my ass right? :))

This email has been scanned for all known viruses by the MessageLabs SkyScan service.

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message