On 12 Jun 2012, at 02:49, Leif Hedstrom wrote: > Another option that I've been pondering, which is more suitable for large > contents I think, is to kick off background requests for the full objects. A > plugin that does something like: > > Thoughts?
I seem to recollect discussing approaches to caching ranges recently (was it with you?) What you outline makes sense where the resource is much bigger than the requested range, and fetching the whole thing (in a rangeless request to the backend) would be too much overhead. But to enforce it on all range requests could be overkill. I wonder if there's a case for adding a heuristic to examine the client's ranges, and fetch the whole thing while the client waits UNLESS the number of bytes the client wants to skip exceeds some threshold - which then triggers what you describe? -- Nick Kew
