This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Websocket address support for Unix Sockets #702
Labels
bug
Broken functionality or incorrect documentation
When hosting a foxglove websocket bridge behind a reverse proxy on the same machine, it would be nice to support unix sockets as a host address/port for the websocket server connection. This could be more efficient than redirecting websocket traffic over local loopback network interfaces, with some web servers now natively supporting unix sockets:
As a bonus, this could improve the overhead performance/latency in Foxglove Studio as well, if compatible with the Electron app, providing a performative alternative to the deprecated native ROS2 bridge that could've used DDS shared memory transport.
As of writing, it looks like the
websocketpp
library used here has a ticket and PR implementation for supporting unix sockets:The text was updated successfully, but these errors were encountered: