But the this.queue array is empty after adding the requests for the first time, so I think runAll is not good until you have... sent all, not sure.
In comparison to other classes in MooTools, I think this one is kind of counter-intuitive. I would kind of expect this class to behave like a composite ( http://en.wikipedia.org/wiki/Composite_pattern) but with a queue behavior upon invoking methods. Just a thought. David On Tuesday, May 28, 2013 1:54:58 AM UTC-4, Sanford Whiteman wrote: > > Yep. other people are also concerned/confused: > > https://github.com/mootools/mootools-more/issues/1158?source=cc > > I think this thing works a bit strangely. You still have to send() > your requests until there are too many concurrents, and only _then_ > will the queue fill up. The queue will also be run automatically, > respecting the concurrent request limit, _unless_ you call runAll, > which circumvents the limit and blasts everything at once. > > At least I think that's it... > > -- S. > > -- --- You received this message because you are subscribed to the Google Groups "MooTools Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mootools-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
