FLEX prematurely purges older items from network debugging cache

[NSExceptional]

FLEX purges older items from the network debugging cache even when the cache is nowhere near full. I would assign this to myself if I could. I would like it to cache them to a temporary file or something, it's super annoying when recent requests are purged for seemingly no reason...

[NSExceptional]

I propose we give this a try as a replacement: https://github.com/nicklockwood/OSCache

Thoughts?

[aleksandergrzyb]

This is not connected to #91?

[NSExceptional]

After reviewing the comments it seems to be related, yeah. What happened there? It's 2 years old

[aleksandergrzyb]

Yeah, I know. 😞 I made a fork and implemented it privately using PINCache for my company internal purposes. The difference is that you cannot opt-out from persistence and PINCache dependency. Unfortunately I didn't have time to implement this and create a PR. I don't think I will have time anywhere soon. 😞

[NSExceptional]

Like disk persistence?

I'm hoping one of the contributors just gives me the OK to use Nick's cache. Anything is an improvement over the paranoid NSCache

[ryanolsonk]

@NSExceptional I've been annoyed by this as well (particularly when backgrounding an app). I'm ok pulling in OSCache if you want to give that a shot.

[NSExceptional]

Awesome. I'll send a PR when I have time to do it.

[hiburn8]

This should be marked as an issue rather than enhancement. Since the user can control the amount of cache space they want to use with a slider (although this is fairly limited given some iOS devices have 4GB of RAM), and they can manually purge the cache, there really is no reason to use NSCache here... it introduces a behaviour that the user doesn't expect.
I would argue we can just use a NSMutableDictionary here and purge it under the behaviour that the user expects.