Should IndexedDB allow indexing on Request/Response properties
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
Reviving an IndexedDB issue from 2019 that we revisited at TPAC 2024, which involves: "allowing Request/Response objects to be stored in Indexed DB. That basically just requires defining serialization for them - a blob plus some metadata."
In 2024, do we have scenarios that need Request/Response support in IndexedDB?
Previous discussions indicate the sync and backgroundfetch events might provide use cases, but the discussion didn't go into much detail.
Contributor guide
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 with the linked IndexedDB issue from 2019 and the previous ServiceWorker discussion about sync and backgroundfetch events. Gather concrete 2024 use cases for storing Request/Response objects and determine whether their serialization should be pursued; a useful outcome is a documented scenario and a clear direction for the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100