>
> Ah, but stopping them is precisely what it appears you want to do. If 200
> requests are going to go out and their responses processed, when in fact all
> you really need is for a single (final) request to go out (i.e. all of those
> first 199 requests and processed responses are simply wasting time), then by
> sending just that one final request, you wouldn't need to display the
> application is busy because it wouldn't remain busy for any obvious amount
> of time, right?
>
> I'll continue to think about this, but I believe at the moment that
> something akin to the timer I first proposed is likely a good option for
> you.
>
> Derrell
>
> I'm working on something like this now, where if the server backlog gets
over a certain threshold, it'll start queuing (and discarding) requests,
saving only the last 'good one' for when things calm down. That should
reduce lag as well as server load substantially. I had tried using a timer
approach before even starting this thread, but javascript timers on top of
the rest of this app. looked incredibly complex; all the samples showed how
easy it was to get "alert('hello world')" to work, but in a real app with
actual classes, etc. it was beyond what I wanted to tackle :-).
Ken
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
