... ok i have this working, but still, it's not optimal to just
increment active timeouts, or is it?
any thoughts here are much appreciated
--------------
// cumulative timeout in msecs
Ajax.activeRequestTimeout = 0;
Ajax.Responders.register({
onCreate: function(request) { Ajax.activeRequestTimeout +=
request.options['requestTimeout']},
onComplete: function(request) { Ajax.activeRequestTimeout -=
request.options['requestTimeout']}
});
...
// and onCreate, register timeout handler on Ajax.activeRequestTimeout
--------------
cheers
--
mona
[email protected]
On Wed, Apr 15, 2009 at 5:41 PM, Mona Remlawi <[email protected]> wrote:
> dear prototypers,
> i have implemented the support for onTimeout in Ajax Responders, and
> it's working like a charm (yeey!)
> the delimma is when we have multiple simaltaneous requests, the
> earlier requests would be slowing down the later requests and thus the
> timeout set on the later requests would be unrealistic.
> i'm wondering what would be a good algorithm to keep the timeout
> values realistic.
>
> cheers
>
> --
> mona
> [email protected]
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~----------~----~----~----~------~----~------~--~---
