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 i have a queue of requests that happen async, this kicks off immediately and any NEW requests don't get fired off .. therefore no flooding will occur. Even better, there is no client wait, unlike the timer scenario as suggested. The end effect is still the same -> server is not getting flooded. I think people are getting confused with what is getting sent to the server. If i have 3 _separate_ parts of my UI (eg. Top 10 movies this week, Top 10 stocks of the week and Top 10 songs of the week) then each one of these will have it's own request. This means that 3 separate asyn ajax requests hit the server. if for some reason, i want to 'pan-pan-pan-pan-pan' which means each one of those ui blocks need to get a refresh of the data ... i want to queue each one separately, not have a queue for ALL 3 .. meaning the movies data refresh is sent off but the stocks and songs data lists are 'waiting' .. that's ludicrous and not what i was saying. Anyways, i think the post has been answered -> jQuery core doesn't have what i want, built in. I need to get a plugin. :)
