Re: [whatwg/encoding] Specify the usage of token queues ("streams") for I/O (#221)

The idea here was to make as few changes as possible to the current model, which already treats a stream with data from I/O as containing the whole content when it's created. Since the only way to tell the current length of the stream is by reading tokens until EOS, I'm treating its contents that come from I/O as spec artifacts unobservable from outside the token queue.

But perhaps this model isn't too easy to understand and it might be best to simply have one special blocking token that, when read, would prepend a token to the queue before it. That's probably far more simple and would better reflect what implementations do.

-- 
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/221#issuecomment-654330771