The queue will be processed, but the rapid storage access causes Chrome to whine, and there should be a better way to show as sites are processed one by one (just having them disappear and letting the m run in the background is a horrible idea). I'd love to have some kind of status indicator as sites are processed, but that means I need a way to pass callbacks all the way down into the XHR dispatching function... I don't know if there's a clean solution for this; I may just end up tearing out queueing. The volume it processes just doesn't seem feasible.
The queue will be processed, but the rapid storage access causes Chrome to whine, and there should be a better way to show as sites are processed one by one (just having them disappear and letting the m run in the background is a horrible idea). I'd love to have some kind of status indicator as sites are processed, but that means I need a way to pass callbacks all the way down into the XHR dispatching function... I don't know if there's a clean solution for this; I may just end up tearing out queueing. The volume it processes just doesn't seem feasible.