Re: [w3ctag/design-reviews] Writable Streams (#163)

> I'm assuming that reader.close() releases the lock and closes the writer, and that subsequent calls to getWriter will create a new writer for the same stream, but I was a bit confused in the spec by the closeRequest slot which gave me the impression that calling close on a writer closes the stream itself.

It's actually `releaseLock()` that releases the lock and detaches the writer. `close()` requests the stream to close. It's possible to call `releaseLock()` while the close is in progress, and the writer will be detached but the close will continue.

I didn't realise that the semantics were confusing. Thank you for the feedback.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/163#issuecomment-297918935