How does a servlet request work. Not a newbie question ;) 2004-01-09 - By Shapira, Yoav
Back
Howdy,
I see three options that fall within the realm of not a huge amount of
work:
- Dig into tomcat source code, extend Coyote in some custom way to
recognize your headers, recognize what you call "load" (which is much
harder to do than recognizing headers), and filter requests
appropriately.
- Create a simple Filter (ServletFilter) that looks for your request
headers, again recognizes "load", and filters requests appropriately
(this filter would be mapped to url-pattern /*). This is far less
efficient than the Coyote solution, because you will reject requests
further along the processing pipeline that you need to, but this
approach is portable.
- Attack the problem with clustering: install more tomcat instances and
a load balancer, ideally one that can assign weights to your workers and
direct requests to workers according to headers. (The balancer webapp
that ships with tomcat 5 has a request header rule that will let you
redirect requests based upon header values -- you'd have to add the
"load" recognition capability).
Yoav Shapira
Millennium ChemInformatics
-- --Original Message-- --
From: Donie Kelly [mailto:donie.kelly@(protected)]
Sent: Friday, January 09, 2004 7:20 AM
To: Tomcat Users List (E-mail)
Subject: How does a servlet request work. Not a newbie question ;)
Hi all
I want to insert some form of scheduling into our application and I was
wondering how Tomcat passes the request to the actual servlet I write.
Does Tomcat just read the headers to create the request object and leave
the body of the message in an inputstream for the servlet to read or is
all the data in the request read by Tomcat before passing it to servlet?
Some of my traffic is more important that other based on headers in the
request. I want to prioritise the handling of requests under load
conditions.
Any input on this is welcome.
Thanks
Donie
This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential, proprietary
and/or privileged. This e-mail is intended only for the individual(s) to whom
it is addressed, and may not be saved, copied, printed, disclosed or used by
anyone else. If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender. Thank you.
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)
|
|
