On Sat, Oct 5, 2013 at 4:57 AM, David Baelde <david.baelde@gmail.com> wrote:
Hi guys,

Requests associated to local files are instantly resolved when
created, so the primary/secondary distinction does not matter.

Chris, if you want to resolve more requests in advance, just increase
the length of the primary queue using the "length" parameter. Most
requests will be considered has having duration "default_duration", so
if you set length to be N*default_duration you should get N requests
resolved in advance.

Thanks David! Yes, this does extend the primary queue length and forces resolution or remote files.  That explains my question... but the problem is that the secondary queue is the editable portion of an request.equeue source.  That said, I could probably script a download/resolve function to fool it into thinking it's a local request.

Appreciate the assistance.