http://www.clientcide.com/code-snippets/ajax/new-plugin-requestqueue/

Same here, firebug doesn’t show the request until it’s already done. And when it’s done, it tells me that it only took 1ms (which can’t be true, I’ve put a sleep(2) in my php). Odd, odd, odd… link: ‘chain’ however works like a charm! I hope they’ll update the docs soon.

My implement is indeed useless. It is not in the documentation, but setting ‘link’:'chain’ does work to chain/queue requests.

After testing I think I have either discovered a MooTools bug, or a Firebug bug, or some other manner of oddity. When using ‘link’:'chain’, I am not seeing a response logged in Firebug, however the response does exist, as I can still use it when passing to the onSuccess function.

So, uh, someone look into that or something.

The check method allows you to queue, cancel or ignore requests while there is already a request running (identical to the Fx classes) depending on the option you provide. (look at the source!)

So to do this, you don’t need to add any code (ie @atom, it is already in the core…)

Simply provide {link: ‘ignore’ | ‘chain’ | ‘cancel’} as required. The default is ignore, so you won’t have seen it and I’ve no doubt it’s not documented yet…
*rolls eyes

Honestly, since the forums were shut this sort of thing seems to be happening a lot.

To implement ‘onChainComplete’ (like you did for the queue), just add an event to onSuccess that checks the length of the chain

ps. I *Adore* your design…

I am pretty surprised that something like this hasn’t made its way into the core yet.