<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000"><div><font size=2 color=navy face=Arial>
It doesn't really matter as 1 second is an arbitrary value that may or may not do what's intended reliably and delay processing. I'd go with Lukas' suggestion of chaining actions via events instead.<br>
<br>-Boris (via BlackBerry)</font></div>
<br><div><hr size=2 width="100%" align=center tabindex=-1>
<font face=Tahoma size=2>
<b>From</b>: seaside-bounces@lists.squeakfoundation.org <seaside-bounces@lists.squeakfoundation.org>
<br><b>To</b>: seaside@lists.squeakfoundation.org <seaside@lists.squeakfoundation.org>
<br><b>Sent</b>: Wed Jul 28 13:21:28 2010<br><b>Subject</b>: Re: [Seaside] How I delayed a Seaside callback to allow a JQuerytoggle effect to happen before the callback.
<br></font><br></div>
<font face="Georgia">That's a thought-provoking comment. </font>How
many concurrent users might one expect a single Seaside image to
support? And how much degradation would one experience if there were
one-second delays inserted in various processes from time to time? I
guess I'm not thinking in the right order of magnitude.<br>
<br>
Cheers,<br>
Bob<br>
<br>
On 7/28/10 12:52 PM, Lukas Renggli wrote:
<blockquote
cite="mid:AANLkTi=Fk9KxKguu4eeGGNKPTKLg7f-Pb6uJed4AmrXf@mail.gmail.com"
type="cite">
<pre wrap="">Keep in mind that this might put quite some load onto the server, if
lots of clients cause their process to wait for one second.
</pre>
</blockquote>
</body>
</html>