Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Jetty/Feature/Quality of Service Filter"
| Line 3: | Line 3: | ||
The blocking nature of the standard servlet API makes it impossible to implement web applications that can guarantee some level of [http://en.wikipedia.org/wiki/Quality_of_service Quality of Service (QoS)]. Threads and memory are limited resources within a servlet container, yet with the standard servlet API, the only way to handle a HTTP request is with a thread allocated for the entire duration of the request. If a request is of low priority, or if other resources needed by the request are not available, then it is not possible to reuse the thread allocated to the request for high priority requests or requests that can proceed. | The blocking nature of the standard servlet API makes it impossible to implement web applications that can guarantee some level of [http://en.wikipedia.org/wiki/Quality_of_service Quality of Service (QoS)]. Threads and memory are limited resources within a servlet container, yet with the standard servlet API, the only way to handle a HTTP request is with a thread allocated for the entire duration of the request. If a request is of low priority, or if other resources needed by the request are not available, then it is not possible to reuse the thread allocated to the request for high priority requests or requests that can proceed. | ||
| body = | | body = | ||
| − | Jetty supports [[Jetty/Feature/Continuations|Continuations]], which allows non-blocking handling of HTTP requests, so that that threads may be allocated in a managed way to provide application specific QoS. The [http:// | + | Jetty supports [[Jetty/Feature/Continuations|Continuations]], which allows non-blocking handling of HTTP requests, so that that threads may be allocated in a managed way to provide application specific QoS. The [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/servlets/QoSFilter.html QoSFilter] is a utility servlet filter that uses [[Jetty/Feature/Continuations|Continuations]] to implement some QoS features. |
| more = | | more = | ||
Check out the QoSFilter [[Jetty/Reference/QoSFilter|reference guide]] for more information and configuration instructions. | Check out the QoSFilter [[Jetty/Reference/QoSFilter|reference guide]] for more information and configuration instructions. | ||
| category = [[Category:Jetty Feature]] | | category = [[Category:Jetty Feature]] | ||
}} | }} | ||
Revision as of 15:24, 28 June 2010
Introduction
The blocking nature of the standard servlet API makes it impossible to implement web applications that can guarantee some level of Quality of Service (QoS). Threads and memory are limited resources within a servlet container, yet with the standard servlet API, the only way to handle a HTTP request is with a thread allocated for the entire duration of the request. If a request is of low priority, or if other resources needed by the request are not available, then it is not possible to reuse the thread allocated to the request for high priority requests or requests that can proceed.
Feature
Jetty supports Continuations, which allows non-blocking handling of HTTP requests, so that that threads may be allocated in a managed way to provide application specific QoS. The QoSFilter is a utility servlet filter that uses Continuations to implement some QoS features.
Additional Resources
Check out the QoSFilter reference guide for more information and configuration instructions.