Skip to content
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

Define "tee" #14

Closed
yutakahirano opened this issue Jan 26, 2015 · 4 comments
Closed

Define "tee" #14

yutakahirano opened this issue Jan 26, 2015 · 4 comments

Comments

@yutakahirano
Copy link
Owner

Request.clone and Response.clone have tee concept though it is not defined. It is not defined in the Stream spec either and I guess it won't be (@domenic, is that correct?) As introducing body grants users more controls, it should be specified more precisely in this spec.
@domenic
Copy link
Contributor

domenic commented Jan 27, 2015

I think the streams spec should probably define this, and eventually user-expose it. Since it is in the ship-ASAP subset, it sounds like I need to prioritize this highly. I will open an issue on whatwg/streams, but would welcome your contribution. I can't get around to it until next week due to TC39 this week.

@domenic domenic mentioned this issue Jan 27, 2015
Closed
@yutakahirano
Copy link
Owner Author

Thank you!

@yutakahirano
Copy link
Owner Author

We don't need a full algorithm for the first release, but specifying important points is desirable. The points being discussed in whatwg/streams#271 need to be specified by the initial release, I think.

@annevk annevk mentioned this issue Mar 30, 2015
Closed
@yutakahirano yutakahirano mentioned this issue Apr 8, 2015
Merged
@yutakahirano
Copy link
Owner Author

Merged. 34d2ccc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@domenic @yutakahirano