Skip to content

Describe "transfer body" algorithm #450

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
yutakahirano opened this issue Jan 6, 2017 · 1 comment
Open

Describe "transfer body" algorithm #450

yutakahirano opened this issue Jan 6, 2017 · 1 comment
Assignees
@ricea
Labels
topic: streams

Comments

@yutakahirano
Copy link
Member

Currently it is described in https://w3c.github.io/ServiceWorker/#dom-fetchevent-respondwith and https://w3c.github.io/ServiceWorker/#dom-foreignfetchevent-respondwith but having the algorithm in Fetch would be helpful.

Note: A refactoring is planned when pipeTo and transform stream is ready (see #330 (comment)). I'll do this work along with the refactoring.
@yutakahirano yutakahirano self-assigned this Jan 6, 2017
@yutakahirano yutakahirano mentioned this issue Jan 6, 2017
Merged
@yutakahirano yutakahirano changed the title Describe "transfer a body" algorithm Describe "transfer body" algorithm Jan 6, 2017
@annevk annevk mentioned this issue Jan 17, 2017
Closed
@annevk annevk mentioned this issue Mar 13, 2018
Closed
@ricea
Copy link
Collaborator

ricea commented Mar 13, 2018 •
edited
Loading

Tentatively self-assigning per discussion with @yutakahirano.

Edit: Okay, I can't actually edit the Assignees. Let's just pretend I did.

Edit 2: Assigned for real this time.

@ricea ricea assigned ricea and unassigned yutakahirano Mar 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ricea ricea

Labels
topic: streams
Milestone
No milestone
Development

No branches or pull requests
3 participants
@annevk @yutakahirano @ricea