PM, Ken Fox k...@vulpes.com wrote:
I'm looking for advice on the best way to map REST requests onto a
collection of Tomcat apps all running in the same JVM. The REST name space
was designed for client use and doesn't reflect how the apps implement it.
For example, the resource /v1/x/123
chuck.caldar...@unisys.com wrote:
If you place the standard rewrite filter in the ROOT context, you can catch
any requests that do not directly map to the appropriate webapp and forward
or redirect them appropriately.
I looked at UrlRewriteFilter and it seemed designed for forwarding within
My company has run Tomcat apps on Amazon's EC2 that have exceeded 1,500 hits
per *second*. We use Amazon's load balancer in front of a variable number of
Tomcat instances (each on their own EC2 instance). For 1,500 hits per day
you probably only need one small EC2 instance running a single Tomcat.
I'm looking for advice on the best way to map REST requests onto a
collection of Tomcat apps all running in the same JVM. The REST name space
was designed for client use and doesn't reflect how the apps implement it.
For example, the resource /v1/x/123 is implemented by app X, but the
resource
On Sat, Aug 21, 2010 at 2:42 PM, Pid * p...@pidster.com wrote:
We don't usually count web traffic in hits any more, because a single
page could easily cause 100 hits.
I think hits to your app servers is still an appropriate way to think
about your server load. If a page view generates 100 hits
