- From: Domenic Denicola <notifications@github.com>
- Date: Thu, 22 Jan 2015 08:59:44 -0800
- To: slightlyoff/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Thursday, 22 January 2015 17:00:14 UTC
> The only real hazard I see with the getter is that you could accidentally start the stream reading process by iterating the Request/Response properties with toJSON() or something. Note that this won't have any script-observable consequences though; it will just cause an IPC. I think part of the issue is that I am used to thinking about things from a self-hosting perspective. In that case there is no "Hey browser, please pass it to the JavaScript world! I want to read it!"---it's all JavaScript world already. I tend to think of developer perceptions of APIs from this perspective too. Which leads to stuff like my comment https://github.com/whatwg/streams/issues/269#issuecomment-71042249 --- Reply to this email directly or view it on GitHub: https://github.com/slightlyoff/ServiceWorker/issues/606#issuecomment-71054920
Received on Thursday, 22 January 2015 17:00:14 UTC