yutakahirano/fetch-with-streams

Issues

• streams as a replacement for progress events... what about upload progress?

  #24 opened 7 years ago by caitp
  8

• Request/Response constructor with a ReadableStream (not ReadableByteStream)

  #44 opened 7 years ago by tyoshino
  3

• Do not conflate IDL ReadableStream and JS ReadableStream implicitly.

  #52 opened 7 years ago by yutakahirano
  4

• Support mixed-content opaque stream fetches

  #56 opened 7 years ago by wolenetz
  26

• Creating service worker responses from multiple readable streams, efficiently

  #59 opened 7 years ago by domenic
  13

• bodyUsed and opacity

  #61 opened 7 years ago by yutakahirano
  6

• Keep "null body" notion

  #39 opened 8 years ago by yutakahirano
  29

• Reuest.body value after passed to another Request

  #60 opened 8 years ago by yutakahirano
  5

• Representing Fetch' body concept in streams, Request side

  #41 opened 8 years ago by yutakahirano
  2

• Uploading: Provide a way to not set Content-Length

  #65 opened 8 years ago by yutakahirano
  2

• Uploading: how to handle redirects

  #66 opened 8 years ago by domenic
  41

• chunked uploads are not possible with http 1.x protocols

  #57 opened 8 years ago by wanderview
  27

• Does any of this require CORS-with-forced-preflight?

  #10 opened 8 years ago by annevk
  11

• Change type to ReadableStream

  #46 opened 9 years ago by annevk
  4

• Excess copying in current spec?

  #67 opened 8 years ago by domenic
  15

• Uploading: write to a writable stream, or pass in a readable stream?

  #30 opened 8 years ago by domenic
  114

• Uploading: allow blobs, or just BufferSource?

  #53 opened 8 years ago by domenic
  13

• Response constructor with ReadableStream

  #63 opened 9 years ago by yutakahirano
  21

• Representing Fetch' body concept in streams, Response side

  #40 opened 9 years ago by yutakahirano
  6

• Preparation for merge

  #25 opened 9 years ago by yutakahirano
  46

• problem with .text() drain behavior and .bodyUsed

  #37 opened 9 years ago by wanderview
  164

• can Response.body.cancel() terminate an ongoing Response.json()?

  #51 opened 9 years ago by wanderview
  4

• Refactor used flag / bodyUsed to use IsDisturbed

  #45 opened 9 years ago by annevk
  0

• body property of Opaque response

  #47 opened 9 years ago by yutakahirano
  1

• Representing Fetch' body concept in streams

  #36 opened 10 years ago by annevk
  13

• Specify life time management

  #15 opened 10 years ago by yutakahirano
  33

• View versus buffer

  #35 opened 10 years ago by annevk
  28

• Need to describe stream's chunk type more clearly

  #31 opened 10 years ago by yutakahirano
  2

• Define "tee"

  #14 opened 10 years ago by yutakahirano
  4

• Put enough clarification about the difference between the associated body and the body attribute of Response/Request class

  #7 opened 10 years ago by tyoshino
  3

• Include some reference to the "lock" concept draft

  #9 opened 10 years ago by tyoshino
  11

• "slow read" feature

  #22 opened 10 years ago by annevk
  7

• Specify stream chunk type.

  #19 opened 10 years ago by yutakahirano
  4

• Specify Fetch function more specifically

  #17 opened 10 years ago by yutakahirano
  1

• Add examples

  #11 opened 10 years ago by tyoshino
  2

• .bodyUsed vs. .locked

  #13 opened 10 years ago by yutakahirano
  4

• Make it clear that the read end is exposed via the body attribute

  #8 opened 10 years ago by tyoshino
  1

• Expose the writable end

  #2 opened 10 years ago by domenic
  3

• Why contentType?

  #1 opened 10 years ago by domenic
  5