Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 49713 invoked from network); 6 Feb 2003 18:11:33 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 6 Feb 2003 18:11:33 -0000 Received: (qmail 7771 invoked by uid 97); 6 Feb 2003 18:13:03 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org Received: (qmail 7764 invoked from network); 6 Feb 2003 18:13:03 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 6 Feb 2003 18:13:03 -0000 Received: (qmail 48240 invoked by uid 500); 6 Feb 2003 18:11:15 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 48217 invoked from network); 6 Feb 2003 18:11:15 -0000 Received: from unknown (HELO ntexchange01.7thonline.com) (66.200.183.106) by daedalus.apache.org with SMTP; 6 Feb 2003 18:11:15 -0000 Received: by ntexchange01 with Internet Mail Service (5.5.2653.19) id ; Thu, 6 Feb 2003 13:09:57 -0500 Message-ID: <6D0DEA16C5F9D311819300D0B74719A3933E12@ntexchange01> From: Bing Zhang To: 'Tomcat Users List' Cc: Dan Yin , Jimmy Wu , Daniel Ruiz Subject: how to block Date: Thu, 6 Feb 2003 13:09:56 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi all: I have one problem right now, which many people here on the list should have already experienced. For example, some post from browser take some time on the server side(servlet code) to process. Often times impatient user will click multiple times on the "submit" button, Or "malicious" user will hold "Enter" key to request it million times. What's going to happen on the server side is: multiple threads onto the same servlet would be launched and resources would be used up, like connections, and CPU processing time. So what's a general approach to prevent this ?? No matter the solution is on the client side (HTML/JavaScript), the server side(servlet/JSP), or combined. Can you guys pass some experience, ideas, thoughts on this ?? Thank you so much. Bing --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org