Michael Joseph Rosenthal

A follow up comment after a few weeks of inactivity would have been appropriate in this case

@lookfirst just trying to promoting good OS etiquette. I guess we have different philosophies on what that constitutes.

One thing we could do is just make the cache's `Map` storage injectable and default it to [`LruMap`](https://api.flutter.dev/flutter/quiver.collection/LruMap-class.html). I think ideally, caching and persistent storage are concerns we externalize/generalize so...

@serendipity1004 you can go ahead with `cache.clear` - I don't think we need `client.cache` is exposed already anyhow, so `client.cache.clear()` will be callable from the client.

@bamoha `client.cache.clear` hasn't been implemented yet, but if you do the following on user log out it should be fine: ```dart client.cache.reset(); // empty the hash map await client.cache.save(); //...

`4.0.0-alpha.7` adds a `client.resetStore` and exposes the `cache.store`. In v4, storage is decoupled from the `cache`, so writing a 3rd party store with eviction capabilities should be straightforward with something...

@kateile given the current design of the cache, which uses [normalize](https://pub.dev/packages/normalize), one would have to go through all keys in the cache to find posts to delete – which is...

hmm – it seems [the `http` library doesn't do automatic redirects by design](https://github.com/dart-lang/http/issues/157#issuecomment-417639249). I guess we could add a flag or link for [following redirects](https://pub.dev/documentation/http/latest/http/BaseRequest/followRedirects.html) every request though

These are interesting proposals - it would help if you could find some analogous proposals or features in `apollo-client`. We mostly try to follow it's designs.

Some discussion on ttl in hive: https://github.com/hivedb/hive/issues/18. We probably need ttl at the cache level so that we have graphql-level awareness of lifespan from @lazylazyllama > I am using Hive...