w3c / w3c/FileAPI

Specify actual byte reading algorithm for Blob.stream()

Open
#194 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
118
Forks
52
Avg merge
9d 16h
Merged PRs (30d)
1

Description

#188 did not really do that.

Also, the currently specified algorithm in https://w3c.github.io/FileAPI/#blob-get-stream is just greedily enqueues everything into the stream but AFAICT both Blink and Gecko read the data asynchronously on read request. It would probably be good to use the new pull from bytes algorithm to fix both problems.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the Blob get-stream algorithm linked in the issue, then compare it with issue #188 and the Streams specification's “pull from bytes” algorithm. The work is complete when Blob.stream() specifies asynchronous byte reading in response to read requests rather than greedily enqueueing all data.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.