I sometimes use these occasions to find out why the RR loop is taking so
long :)

In other words, is it possible to move your process logic outside of the
RR loop? Sometimes it's just not possible (or desirable), and you may
want to disable the caller client-side as discussed. Other times you
could spawn a task (directly or not directly related to your view).

--
Matt
http://logicsquad.net 


On Fri, Feb 6, 2015, at 04:07 PM, Chuck Hill wrote:
> Users are more certainly a general problem!  :-)
> 
> I am not aware of anything in WO or Wonder to prevent this.  Usually 
> processing is quick and re-clicking is of little consequence or easy to code 
> around..  Just wait until you hit this with the AjaxModalDialog when they 
> click on something in the dialog
 after clicking a close link and before the dialog closes.  Lots and
 lots of fun to be had with this one.
> 
> Another fun aspect is that unless this is Ajax, only the result of the last 
> click will be used by the browser.  So you can’t just short circuit clicks 
> 2..N.   javascripts to catch the clicked link and disable it immediately is 
> probably your best bet.
> 
> Enjoy!
> 
> Chuck
> 
> 
> 
> On 2015-02-05, 8:47 PM, "OC" wrote:
> 
>> Hello there again,
>> 
>> I might be wrong, but from analysis of my last log it seems at least one of 
>> the users got the stupid idea that clicking again on a link whose response 
>> was not immediate might speed things up.
>> 
>> I frankly admit I never ever tried that -- after all, who would even think 
>> of clicking links whilst the page is being reloaded?!? To me, it does not 
>> make any sense. Anyway I've just tested, and found instead of doing nothing 
>> (which would seem the reasonable
 thing to do) it simply creates and runs a new R/R loop each time the
 link gets clicked, regardless the page is already being reloaded for
 tens of seconds. Wow.
>> 
>> Thus the aforementioned user started another R/R loop. And another. And 
>> another. And so forth. The more concurrent threads did the same thing, the 
>> slower they got. Oops.
>> 
>> I guess I could rig some javascripts to catch the clicked link and disable 
>> it immeditely or something like that; but it would be some legwork to do 
>> properly. I wonder, this being self-evidently a general problem, whether 
>> there might already be a solution
 in WOnder?
>> 
>> Thanks,
>> OC
>> 
>> 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      ([email protected])
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/chill%40gevityinc.com
>> 
>> This email sent to [email protected]
> 
> _________________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/matt%40logicsquad.net
> 
> This email sent to [email protected]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to