Skip to content

Commit 63cb959

Browse files
Mlaz-codeclaude
andcommitted
docs(readme): correct latency comparison
The "~100ms vs 1-2s for SSE" line wrongly framed WS as faster than SSE — both are push-based with comparable end-to-end latency. The "1-2s" number applies to REST polling. Reframe so the comparison is WS-push vs REST-polling, and surface the real WS-vs-SSE tradeoff: bidirectional control vs simpler unidirectional streaming. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 parent dc4e22b commit 63cb959

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ stream.disconnect()
6666

6767
## WebSocket Streaming
6868

69-
Lower latency (~100ms vs 1-2s for SSE):
69+
Real-time push (~100ms vs 1-2s for REST polling). SSE delivers comparable latency — pick WS for bidirectional control (subscribe/unsubscribe, filter updates) or SSE for simpler one-way streaming behind firewalls:
7070

7171
```typescript
7272
const stream = api.stream.oddsWs({

0 commit comments

Comments
 (0)