Something else to consider is configuring two connection thread queues for your server. AOLserver 4.x allows you to map URL's to a particular pool of connection threads.
One could imagine configuring two pools: one pool with say 10 max connection threads to handle the "slow" requests (PUTS), and a second pool to handle the "fast" requests (PROPFIND). Doing this will provide a little more isolation, and ensure your server doesn't thread max only handling the "slower" PUTS requests. This is a lot like resource quotas. There is a configuration example in the sample-config.tcl file towards the bottom. Let me know if there are any questions. - Nathan Brady Wetherington wrote on 5/12/2004, 3:35 PM: > My concern would be resource starvation attacks possible if > someone requested a large response, but didn't actually 'take' any of the > response - thus forcing the server to cache up a large file, possibly > many > of them. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
