Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Caching of components locally to avoid requesting components twice #129
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?
This comment has been minimized.
This comment has been minimized.Show comment Hide comment
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.