max-mapper / max-mapper/zimmer
Is it practical to read zim files over HTTP?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 14
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
Sorry for the question - not directly related to the module (will be, if the answer is positive) - but is it practical to read zim files over http
More specifically, I imagine something like reading the header by only fetching the a few mb's from the beginning of the file, and then jumping to entries/clusters, as the API allows - is that practical over http, or does it require too many byte seeks/too much downloaded data?
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 reviewing the parser's public API and its handling of ZIM headers, entries, and clusters. Investigate whether HTTP range requests can provide the required byte access, then document the feasibility and any scope for supporting remote ZIM files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100