Cache resource sets when they are fetched

[gra-moore]

At the moment we are always going back to the server to get instances of a type. This is painful after viewing a single entity and then going back to choose another.

If we go back to the start page then we can throw away any cached data.

[kal]

Caching should probably be guided by what the server says - e.g. if they
say cache for 10 minutes, then that's all we do. Is there any underlying
HTTP client cache that we can make use of ?

On Thu, Nov 8, 2012 at 3:50 PM, Graham Moore notifications@github.comwrote:

At the moment we are always going back to the server to get instances of a
type. This is painful after viewing a single entity and then going back to
choose another.

If we go back to the start page then we can throw away any cached data.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1.