We know about this requirement. This needs some discussion on how
exactly the API for caching range requests should look like and what
should the behavior exactly be.
-hb-
On 10/28/2013 11:04 PM, Jason Duell wrote:
On 10/28/2013 02:14 PM, Brendan Dahl wrote:
Is there anyone in the networking group that has time to work on
caching range requests? PDF.js always uses range requests if the
server supports it and if a PDF is reloaded(or navigated to/from) it
takes awhile since all the requests must be resent. PDF.js could
cache the PDF, but it seems it would be better to allow the
networking layer to handle this.
relavent bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=626027
This would definitely be something we add only for the new HTTP cache,
which is in progress. I think it needs to be a followup for after we
land the initial rewrite. But I support the idea of the feature--it
seems like a good one to have, and knowing that we have a common use
case bumps the priority, so thanks for bringing it up.
cc-ing Honza and Michal in case they've got any opinions here.
Jason
_______________________________________________
dev-tech-network mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-network
_______________________________________________
dev-tech-network mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-network
