Since I joined discussion recently, I don't know the original idea behind the Stream+XHR integration approach (response returns Stream object) as in current Streams API spec. But one advantage of it I come up with is that we can keep change to those producer APIs small. If we decide to add methods for example for flow control (though it's still under question), such stuff go to Stream, not XHR, etc.
- Re: Overlap between StreamReader and FileReader Aymeric Vitte
- Re: Overlap between StreamReader and FileReader Takeshi Yoshino
- Re: Overlap between StreamReader and FileReader Kenneth Russell
- Re: Overlap between StreamReader and FileReader Takeshi Yoshino
- Re: Overlap between StreamReader and FileReader Aymeric Vitte
- Re: Overlap between StreamReader and FileReader Takeshi Yoshino
- Re: Overlap between StreamReader and FileReader Aymeric Vitte
- Re: Overlap between StreamReader and FileReader Takeshi Yoshino
- Re: Overlap between StreamReader and FileReader Takeshi Yoshino
- Re: Overlap between StreamReader and FileReader Aymeric Vitte
- Re: Overlap between StreamReader and FileReader Takeshi Yoshino
