FLEXTool/FLEX

FLEX prematurely purges older items from network debugging cache

Open

#173 opened on Feb 25, 2017

View on GitHub
 (8 comments) (3 reactions) (0 assignees)Objective-C (14,597 stars) (1,777 forks)batch import
bugenhancementhelp wanted

Description

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...

Contributor guide

Tech stack
objective c
Domain
mobiledeveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Objective C knowledgeFamiliarity with FLEX architectureUnderstanding of in memory cache behavior
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate the caching mechanism in FLEX's network debugging module, likely in files such as FLEXNetworkTransactionCache or similar. Look for the cache size limit and purging logic. Consider implementing a temporary file based cache expansion to prevent premature purging. Check if there are any related issues or PRs (e.g., #173 comments) for prior attempts.