- From: Kinuko Yasuda <notifications@github.com>
- Date: Mon, 06 Apr 2015 20:10:48 -0700
- To: w3c/quota-api <quota-api@noreply.github.com>
Received on Tuesday, 7 April 2015 03:11:18 UTC
Moved from https://github.com/kinu/quota-api/issues/11: by @wanderview "I understand blink plans to add file de-duplication for their Cache API implementation. My impression is they are planning to de-duplicate across both Cache API origins and the http cache, but I'm not sure. How should the quota system account for de-duplicated files? What happens if an origin thinks they are within their quota, but then the http cache ages out a de-duped file causing it to be solely owned by that origin? Does its usage suddenly go up and trigger further quota eviction?" --- Reply to this email directly or view it on GitHub: https://github.com/w3c/quota-api/issues/1
Received on Tuesday, 7 April 2015 03:11:18 UTC