* The current World-Wide Web service model treats all requests equivalently, both while being processed by servers and while being transmitted over the network. For some uses, such as web prefetching or multiple priority schemes, different levels of service are desirable. This paper presents three simple, server-side, application -level mechanisms (limiting process pool size, lowering process priorities, limiting transmission rate) to provide two different levels of web service (regular and low priority). We evaluated the performance of these mechanisms under combinations of two foreground workloads (light and heavy) and two levels of available network bandwidth (10Mb/s and 100Mb/s). Our experiments show that even with background traffic sufficient to saturate the network, foreground performance is reduced by at most 4-17%. Thus, our user-level mechanisms can effectively provide different service classes even in the absence of operating system and network support. 1. Introduction The ...

* The current World-Wide Web service model treats all requests equivalently, both while being processed by servers and while being transmitted over the network. For some uses, such as web prefetching or multiple priority schemes, different levels of service are desirable. This paper presents three simple, server-side, application -level mechanisms (limiting process pool size, lowering process priorities, limiting transmission rate) to provide two different levels of web service (regular and low priority). We evaluated the performance of these mechanisms under combinations of two foreground workloads (light and heavy) and two levels of available network bandwidth (10Mb/s and 100Mb/s). Our experiments show that even with background traffic sufficient to saturate the network, foreground performance is reduced by at most 4-17%. Thus, our user-level mechanisms can effectively provide different service classes even in the absence of operating system and network support. 1. Introduction The ...