@meshstream/p2p-web 1.0.1 → 1.0.3

package/README.md

@@ -53,6 +53,14 @@ The SDK fetches SaaS bootstrap configuration, selects trackers/reporting
 endpoints, detects browser capability, starts WebRTC P2P when possible, and
 keeps CDN playback as the automatic fallback path.
 
+The SDK starts bootstrap immediately, but does not wait for a network round
+trip before starting media playback. The player uses CDN while the control
+plane is pending or unavailable; the request continues in the background and
+transient failures are retried. A cached or already-resolved bootstrap can
+enable P2P in the current session, while a later playback can use P2P after a
+successful network bootstrap. This startup policy is internal and requires no
+customer configuration.
+
 When MeshStream creates hls.js, use `hlsConfig` to retain normal player tuning
 such as `maxBufferLength`, ABR limits, or low-latency settings:
 
@@ -461,9 +469,11 @@ starting a fresh session for a different source or player lifecycle.
 
 `start()` returns `{ mode, capability, fallbackReason? }`. On a CDN fallback,
 `fallbackReason` is one of `CAPABILITY_UNSUPPORTED`, `P2P_DISABLED`,
-`SDK_CONFIG_UNAVAILABLE`, `TRACKER_UNAVAILABLE`, or
+`SDK_CONFIG_PENDING`, `SDK_CONFIG_UNAVAILABLE`, `TRACKER_UNAVAILABLE`, or
 `P2P_INITIALIZATION_FAILED`. It is intended for customer telemetry and does
-not expose the server bootstrap configuration.
+not expose the server bootstrap configuration. `SDK_CONFIG_PENDING` means
+playback started on CDN before the first bootstrap request settled; it does
+not trigger `onP2pUnavailable`.
 
 `addEventListener()` accepts `onPlaybackStateChanged`, `onP2pReady`,
 `onP2pUnavailable`, `onPeerCountChanged`, `onTrackerError`,