Caching of components locally to avoid requesting components twice #129

Closed
foca opened this Issue Aug 22, 2012 · 1 comment

Comments

Projects
None yet
2 participants
@foca

foca commented Aug 22, 2012

Any reason why this isn't done in Monocle? It's simple enough to cache the results of component loads on the BookDataObject, but I'm not sure why this isn't done in Monocle transparently.

Specially ebooks that have a lot of small components suffer from unnecessary delays when going back and forth through the book.

Is there any reason (philosophical or technical) I'm missing for this or would you welcome a PR?

@joseph

This comment has been minimized.

Show comment Hide comment
@joseph

joseph Aug 27, 2012

Owner

It's not done in Monocle because, as you say, it's simple to do it in getComponent, and not everyone wants to store the data in localStorage. Some people have concerns that their content is compromised if it is locally stored. Others don't want to overload the caches of their visitors with massive amounts of use-once data. Others want to use a different cache, like applicationCache or Gears or whatever.

Owner

joseph commented Aug 27, 2012

It's not done in Monocle because, as you say, it's simple to do it in getComponent, and not everyone wants to store the data in localStorage. Some people have concerns that their content is compromised if it is locally stored. Others don't want to overload the caches of their visitors with massive amounts of use-once data. Others want to use a different cache, like applicationCache or Gears or whatever.

@joseph joseph closed this Aug 27, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment