You may give this plugin a try:
http://plugins.jquery.com/project/ajaxq
partner56290674 wrote:
Hi folks,
can anyone help me with some links to queuing up ajax requests
using jQuery please? I tried using the Ajax Queue plug-in (http://
plugins.jquery.com/project/ajaxqueue) but this wasn't
Fair point Wick, but I did understand what Shawn said and yes, you're
100% correct about your understanding of the question, btw :)
Your suggesting that by implementing a TIMER WAIT, this prevents the
client from FLOODING the server with 'useless requests'. Yep that's
right! 100% right. Now, if
or, blockUI the interface on each click and load once per click. This
will mean the user has to space their clicks out because they CANT
click more times.
On Jul 17, 7:39 am, wick [EMAIL PROTECTED] wrote:
partner[etc],
Currently, when the pan ends, an onEnd event is fired, which then
fires
partner[etc],
Currently, when the pan ends, an onEnd event is fired, which then
fires off the ajax. So what you're suggesting is that i queue the pan
onEnd events?
Nope, I think. Back to your pan-pan-pan-pan-pan situation, doing
what you suggest would still fire 5 times (onEnd fires after
it's possible to possibly wait for the user to stop panning.
Currently, when the pan ends, an onEnd event is fired, which then
fires off the ajax. So what you're suggesting is that i queue the pan
onEnd events?
secondly, i still am confused to why u think jQuery should not offer
this support
partner56290674 wrote:
secondly, i still am confused to why u think jQuery should not offer
this support because you believe this is bad. Remember, the idea of
I think it is inappropriate because you are describing an application
specific issue. Not all applications will have the same
On Tue, 2008-07-15 at 21:46 -0700, partner56290674 wrote:
it's possible to possibly wait for the user to stop panning.
Currently, when the pan ends, an onEnd event is fired, which then
fires off the ajax. So what you're suggesting is that i queue the pan
onEnd events?
I recently needed some
I suppose shawn we can just agree to disagree because your comments
about it's application specific, IMO, is completly misguided in this
topic. IMO, it's not application specific but a option for any
developer to use. I don't see it as something very specific, no more
than jquery having an @each
what your doing there Shawn is still flooding the server with ajax
calls, and displaying them as they come back to the user. What happens
if some requests come back out of order (eg. latency)?
now if u switched it around .. that might be usable...
so there's nothing built in to jQuery? Is
the flooding the server with calls is a non argument. If you don't
want to do that, then you need to redesign your server side code to
accept a single request to give you all the data you need. One call,
one response then. But that's a server issue. And there are
performance/modularity
the flooding the server with calls is a non argument. If you don't
want to do that, then you need to redesign your server side code to
accept a single request to give you all the data you need
Not true .. well at least I don't see it as that. I have no probs with
multiple calls hitting the
Your situation is clearer now. I would think though that the solution
is a little simpler. Bear with me as I talk through this, but I haven't
had the joys of working with google maps like this (yet)...
So, user loads the page. Then user starts panning around. Rapidly.
Instead of trying
What I did was to build an object that would hold the results of each
ajax request. I added on a function that would check when all the
objects were populated, and then call the routine that would handle all
the data.
Something like this (note I'm NOT using the ajax_queue plugin):
var
13 matches
Mail list logo
