Quote:
Originally Posted by Quoth
How?
|
snip
Quote:
What exactly would you cache for about 16,000 epub books (which might easily fit on 32G), or even around 2,000 ebooks in about 4G flash?
How long would building the hypothetical cache take when adding 10 or 100 ebooks?
How much storage would it take?
|
I don't think you quite understand what a cache is (or can be).
It is an area of storage where you store information
that you think may be used in the near future.
Whilst you can cache information from every instance of a data set, if it's impractical (e.g. speed, space), you simply don't.
In the case of an ebook, I would pre-render a few pages ahead (at any point during the read), and store a few <n> books worth, on a first in first dumped basis.
That way, when the user stops reading, for whatever reason, unless s/he opens n-1 or more other books, the one just left is available for immediate start.
I have implemented similar schemes for data-sets, including some where significant processing or decompression takes place, and it works flawlessly.
It's not really a problem for the first read (or reopening after a long pause) of a book that is a problem. It's if you have several books on the go and are swapping frequently, or you have some other reason to go to, say, the home page..
It's interesting that kindles don't have this problem.