Feature: Chrome Direct Sockets API

[nickchomey]

Proposed change

This is just a sort of tracker issue for Chrome's experimental Direct Sockets API, which

Allows Isolated Web Apps to establish direct transmission control protocol (TCP) and user datagram protocol (UDP) communications with network devices and systems as well as listen to and accept incoming connections.

Motivation
Many network devices use their own protocols over TCP or UDP, instead of using HTTPS.

Like WebUSB, WebMIDI and WebBluetooth, this API allows web apps to communicate with local devices and information systems.

Use case

Could do NATS over nats:// protocol rather than ws://

Contribution

No response