You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Commit 24d2560 was pushed to main by mistake: it captured an in-progress
moq-native Client::connect / reconnect refactor under an unrelated commit
message ("classify malformed auth-API JSON ...") and bypassed review. This
reverts those changes so the refactor can land properly via its own PR. The
original change is preserved in history at 24d2560 for re-use.
This reverts commit 24d2560.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The default configuration uses system TLS roots, enables WebSocket fallback, and gives QUIC a 200ms head-start.
30
30
31
-
`connect_once` makes a single attempt and resolves to a session. For most apps prefer `client.connect(url)`, which stays connected and reconnects with exponential backoff whenever the session drops, returning a [`Reconnect`](https://docs.rs/moq-native/latest/moq_native/struct.Reconnect.html) handle.
32
-
33
31
### URL Schemes
34
32
35
33
The client supports several URL schemes:
@@ -41,7 +39,7 @@ The client supports several URL schemes:
41
39
42
40
### Transport Racing
43
41
44
-
`client.connect()`and `client.connect_once()`automatically race QUIC and WebSocket connections.
42
+
`client.connect()` automatically races QUIC and WebSocket connections.
45
43
QUIC gets a configurable head-start (default 200ms); if it fails, WebSocket takes over.
46
44
Once WebSocket wins for a given server, future connections skip the delay.
0 commit comments