Content-Length: 211085 | pFad | http://github.com/zeek/zeek/issues/4136

1A Add WebSocket support for any cluster backends · Issue #4136 · zeek/zeek · GitHub

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add WebSocket support for any cluster backends #4136

Open

awelzel opened this issue Dec 18, 2024 · 0 comments

Assignees

Labels

Milestone

Contributor

awelzel commented Dec 18, 2024 •

edited

Loading

The WebSocket functionality provided to external applications to connect with a Zeek cluster today is provided by the Broker/broker component.

Goal:

The WebSocket component is independent of Broker, lifted into Zeek and uses a cluster::Backend instance.
The protocol and serialization should adhere to the current Broker implementation. https://docs.zeek.org/projects/broker/en/current/web-socket.html
In the future, clients should be allowed to communicate the preferred protocol/serialization by choosing an appropriate WebSocket subprotocol value.

References to external libraries:

IXWebSocket is used by zeek-agent, provides a server component. The README contains a list of alternative open-source libraries.
- The server component starts a new thread per websocket client.
- This might just be fine, but will need a bridge into Zeek's event loop.
libwebsockets

The text was updated successfully, but these errors were encountered:

awelzel added the Type: Project label

awelzel added this to the 7.2 milestone

awelzel self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment