Direct Sockets in Shared Workers

[Andrew Rayskiy]

Hi Blink API Owners,

I'd like to experiment with extending Direct Sockets support (previous ITS) from the current (Window,DedicatedWorker) to also include SharedWorker. I presume this falls into the "extending existing features" bucket and requires an explicit approval; are, however, separate explainer and chromestatus entry also necessary here? Or can I simply send an intent-to-prototype based on the existing explainer / spec / chromestatus?

Thanks,

Andrew

[Domenic Denicola]

I think for an Intent to Prototype, you should be able to just reply to the previous I2S and give people a heads-up about the exposure. I2Ps don't require any approval, and we don't want to make them a heavyweight process.

The eventual I2S is more interesting. I think either approach could work, but since shared workers are pretty different from windows/dedicated workers (e.g. around permissions), I suspect a new ChromeStatus entry would work best.

In particular, I'd expect a discussion of: security/privacy implications of this new exposure; debuggability; web developer signals/what's the motivation for doing this. And we'll want to see artifacts like: the spec PR that adds this exposure, the WPTs that cover this exposure, the new Finch flag this is launched under; and a design doc if there is one.

So to be concrete, I'd recommend sometime between now and I2S:

• Updating the existing explainer with a small section on shared worker behavior (or maybe worker behavior in general)
• Updating the spec
• Creating a new ChromeStatus entry to encapsulate all the stuff I mention above

and then you can use this new ChromeStatus entry to generate the I2S email.

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CACZWnOrnJ1Nxqx4heUj71K9mr0mzZuixz4MY1bjZp7_53Ov4pQ%40mail.gmail.com.