From b9569cb06fd188b32b8a557dcdef24c30274a545 Mon Sep 17 00:00:00 2001 From: Arne Welzel Date: Tue, 15 Apr 2025 15:18:55 +0200 Subject: [PATCH] cluster/websocket: Remove comment about broker --- src/cluster/websocket/WebSocket.cc | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/src/cluster/websocket/WebSocket.cc b/src/cluster/websocket/WebSocket.cc index 0d8e5421ca..e6b867e32f 100644 --- a/src/cluster/websocket/WebSocket.cc +++ b/src/cluster/websocket/WebSocket.cc @@ -257,18 +257,7 @@ void WebSocketEventDispatcher::QueueReply(WebSocketReply&& reply) { reply_msg_thread->SendIn(new ReplyInputMessage(std::move(reply))); } -// WebSocketDemux::Process() runs in the main thread. -// -// XXX: How is this going to work with class broker? With -// ZeroMQ, each WebSocket client has its own XPUB/XSUB -// connectivity to a central broker and similarly with NATS. -// But with broker we need to do something different. -// Maybe connect to the local endpoint. -// -// We cannot actually instantiate a Broker backend :-( -// -// We could also have InitPostScript() recognize Broker -// and start its internal server instead. +// Process a WebSocketEvent message on the Zeek IO loop. void WebSocketEventDispatcher::Process(const WebSocketEvent& event) { std::visit([this](auto&& arg) { Process(arg); }, event); }