Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457)

>> I expect you to define Request.duplex altogether.

> I don't quite understand. Are you saying to not introduce the Request.duplex attribute in this PR, and instead do that as part of https://github.com/whatwg/fetch/issues/1254?

Right, because I don't see a reason to specify it now, and I see a reason not to specify it now.

Specifically,

 1. Until #1254 is resolved, web developers cannot use `Request.duplex` effectively, as it always returns 'half'.
 2. If we fail to specify #1254, it will be difficult to remove the member without compatibility problems.

This is different from the situation for `RequestInit.duplex`.

 1. `RequestInit.duplex` forces web developers to specify the member (when the body is a stream), and that will allow us not to specify the default value for now.
 2. We can remove `RequestInit.duplex` if we fail to specify #1254. There will not be any compatibility problems.




-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1457#issuecomment-1160292595
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1457/c1160292595@github.com>