Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: WebApp really slow, Where do I start looking?
Date: Fri, 1 Jun 2007 12:13:04 +0100
Message-ID: <DDBBD1E00935D144AB9563D57EF98D624EF344@raccoon.melandra.net>
Thread-Topic: WebApp really slow, Where do I start looking?
Thread-Index: AcekKzouoixHoeSkS6uzNdsTh7zMUQACuvnwAAHO04A=
References: <465FDD74.7020301@omegames.com> <465FDFDF.7070301@oma.be>
 <002c01c7a437$1c820cb0$9300a8c0@siege.omegames.com>
From: "Peter Crowther" <Peter.Crowther@melandra.com>
To: "Tomcat Users List" <users@tomcat.apache.org>

> From: St=E9phane Hanser [mailto:s.hanser@omegames.com]=20
> However, removing some synchronized blocks will cause=20
> concurrent access
> issues when a user "mass clicks". Is it possible to configure=20
> tomcat to
> queue one's requests instead of executing the in parallel ?

Not in all cases.  The browser is free to make new requests to a web =
server; it would be up to your code to detect that they came from the =
same session and take appropriate actions.  In general, if a user =
mass-clicks, you actually want to process the most recent as the browser =
will no longer take responses fr the older requests...

If you're concerned about multiple clicks on submit buttons, there are =
well-known ways to use Javascript to disable the button once the user =
clicks it the first time.

		- Peter

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org