Introduce asset module session manager
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Follow up from #2506
Currently, there is no session management, session ids are generated in a potentially conflicting way based on the module index. Sessions can never include multiple modules.
The session management should mimic the original behavior, that is have an ever increasing session id where each download request creates a new session id that covers all modules requested.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #2506 and tracing the asset module download request flow; the payload names no files or tests. Confirm how sessions currently derive IDs and how module requests are grouped. Done means each download request receives a new ever-increasing session ID shared by all requested modules, matching the original behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100