Confirmed users
431
edits
Necko/Cache/Plans: Difference between revisions
→Primary Design Goals
(→People) |
|||
| Line 36: | Line 36: | ||
** Temporal layout so that sub-resources are together. | ** Temporal layout so that sub-resources are together. | ||
** Don't over-optimize on-disk storage, use one file per entry and let OS optimize. | ** Don't over-optimize on-disk storage, use one file per entry and let OS optimize. | ||
* Layered design should include XPCOM API, C++ API exposed to Gecko, middle layer with general cache logic, and back-end allowing for alternative on-disk formats. | * Layered design should include XPCOM API, C++ API exposed to Gecko, middle layer with general cache logic, and back-end allowing for alternative on-disk formats. | ||
* Separate services for HTTP and offline cache? Find a way to make these use cases work well without over-complicating code. | * Separate services for HTTP and offline cache? Find a way to make these use cases work well without over-complicating code. | ||