zeek/testing/btest/Baseline/cluster.websocket.three
Arne Welzel 888af244b2 btest/cluster/websocket: Harden multi-client tests
These test were very sensible to the speed at which ZeroMQ distributes
subscriptions in the cluster and showed to be unreliably when testing with
zeek/btest#113.

The main fix here is to have individual WebSocket clients subscribe to unique
topics, e.g /test/client-0 and /test/client-1, instead of just a shared topic.

This ensures the WebSocket handshake completes only when they observed their
own subscriptions and not prematurely when observing the shared topic.

This seems mainly relevant for tests: In the real world one shouldn't
rely on subscription visibility - you miss messages if you're too late
to the party.
2025-03-24 18:36:26 +01:00
..
..client..stderr cluster/websocket: Implement WebSocket server 2025-03-10 17:07:30 +01:00
..client.out cluster/websocket: Implement WebSocket server 2025-03-10 17:07:30 +01:00
..manager..stderr cluster/websocket: Implement WebSocket server 2025-03-10 17:07:30 +01:00
..manager.out.sorted btest/cluster/websocket: Harden multi-client tests 2025-03-24 18:36:26 +01:00