Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127)

> I'm not fully familiar with Streams. Where do the string chunks in the rechunker example cross the WebIDL boundary (if anywhere)?

Sorry for not explaining clearly. The chunks don't cross the WebIDL boundary within the rechunker example. It's only if you then pipe the stream to TextEncoder or some other stream defined in a WebIDL-based standard that the chunks will cross the WebIDL boundary.

>  The controller seems to be expressed in ECMA spec style and not in WebIDL style. Is there really no WebIDL boundary here and the prose sentence "Let input be the result of converting chunk to a DOMString." defines the boundary that is usually expressed in WebIDL?

I think that is correct. My intent is for "converting chunk to a DOMString" to imply the same processing that would normally happen upon calling a WebIDL method. Is this something that needs to be made more explicit? The same applies to the first step of the "decode and enqueue a chunk" algorithm.

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