[Seaside] How I delayed a Seaside callback to allow a
JQuerytoggle effect to happen before the callback.
Boris Popov, DeepCove Labs (YVR)
boris at deepcovelabs.com
Wed Jul 28 20:26:27 UTC 2010
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.
-Boris (via BlackBerry)
From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces at lists.squeakfoundation.org>
To: seaside at lists.squeakfoundation.org <seaside at lists.squeakfoundation.org>
Sent: Wed Jul 28 13:21:28 2010
Subject: Re: [Seaside] How I delayed a Seaside callback to allow a JQuerytoggle effect to happen before the callback.
That's a thought-provoking comment. 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.
On 7/28/10 12:52 PM, Lukas Renggli wrote:
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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside