Future Support for Low-Level Network APIs in Chrome Extensions

[nifty]

Question
I have a question about the future of the chrome.socket API and alternatives for implementing WebRTC signaling in Chrome extensions.

Current Status and Background
We are currently developing a Chrome Extension that operates under Windows 11 SE environment, and we would like to realize real-time video and data communication using WebRTC with multiple monitors in a LAN. In this system, the Chrome extension on the controller side functions as a server for WebRTC signaling (exchange of SDP and ICE Candidate), and the Chrome extension on the monitor side is supposed to connect to it as a client.

Due to limitations of the development environment, it is not possible to set up an external server such as Node.js or Python on the controller side. Therefore, it is necessary to have a TCP socket server function directly within the Chrome extension.

Currently, the only socket API available to Chrome extensions is chrome.socket, which is deprecated.

Questions
Future support and deprecation of the chrome.socket API:.

The chrome.socket API is currently deprecated, but is there any plan to remove it completely from Chrome extensions in the future?
If so, is there a specific timeline for its removal, and are there any plans to provide an alternative API for equivalent low-level network communication functionality (especially TCP server functionality) within Chrome extensions?
Recommended approach for intra-LAN signaling in Chrome extensions:.

Are there any best practices that Google recommends for Chrome extensions to perform WebRTC signaling (SDP or ICE Candidate exchange) with other extensions in the LAN in environments where an external server is not available?
Regarding recommendations for specific environments:.

Are there any recommended approaches to ensure stable intra-LAN communication for Chrome extensions in environments with specific OS constraints (e.g., unavailability of Win32 API), such as Windows 11 SE?


We would be grateful if you could provide us with your official view and development policy to help us build a stable system in the long term under these circumstances.

Yu Tsumu (nifty)

[Oliver Dunk]

Hi Nifty,

The `chrome.socket` API is a Chrome Apps API, and isn't available in Chrome Extensions. Chrome Apps are already being deprecated - they aren't available on most platforms and the ChromeOS timeline for end of support is here: https://support.google.com/chrome/a/answer/15950395

We don't currently have any plans to provide an equivalent API in Chrome Extensions. It's something I would personally love to see (I think an email client as a Chrome Extension would be really cool!) but traditionally there hasn't been much appetite for exposing such a low-level capability in JavaScript.

I don't have any suggestions specific to WebRTC I'm afraid. In general, if you need a platform capability which isn't available as a Chrome Extension API, we usually recommend native messaging: https://developer.chrome.com/docs/extensions/develop/concepts/native-messaging. That may or may not work in your case depending on what you are able to set up in the Windows environment.

I hope this is helpful.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/373c8927-8a5a-4037-8d83-52ee0be808can%40chromium.org.