The MooTools Request class gives us the option to link together requests so that with a single instance of the class, if you’ve got a request that’s running you can ’stack up’ any new send requests so that they occur one after the other.
This is convenient, but what if you have numerous instances of Request or its subclasses (like Request.HTML) and you want to only have one request running at a time? Or only two?
That’s basically all that Request.Queue does. It lets you register any number of instances of Request or its subclasses with an instance of Request.Queue and then write your code like normal. All requests to server will be queued up and fired off one or two or three at a time (you choose).
Related Submissions:
- Get Tweets with MooTools’ Request.Twitter MooTools Core Developer Scott Kyle appden created Request.Twitter, a very small MooTools class to retrieve tweets from Twitter. The class is flexible in that you...
- Monitor the Scroll with e24ScrollEvents for Mootools e24ScrollEvents is a plug-in for Mootools that lets detect which elements are visible inside an scrolling area. To accomplish this it adds two new events...
- MooTools Plugin: Class.refactor All that Class.refactor does is allow you to assign new properties to a class in the same manner as extending the class onto itself...
- Object Oriented jQuery with MooTools Here’s the recipe: MooTools modules Native, Class, and Class.Extras; jQuery; and Class.Mutatotors.jQuery. Write a MooTools Class and use jQuery for the DOM. Class.Mutatotors.jQuery: This mutator...
- MooTools TwitterGitter Plugin Everyone loves Twitter. Everyone loves MooTools. That’s why everyone should love TwitterGitter, a MooTools plugin that retrieves a user’s recent tweets and allows the user...