@3dsource/angular-unreal-module 0.0.146-dev.6 → 0.0.146-dev.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@3dsource/angular-unreal-module",
-  "version": "0.0.146-dev.6",
+  "version": "0.0.146-dev.8",
   "description": "Unreal module for connect with unreal engine stream",
   "keywords": [
     "3dsource",

package/types/3dsource-angular-unreal-module.d.ts

@@ -1214,6 +1214,17 @@ declare class StreamStatusTelemetryService2 {
     private readonly disconnectReason$;
     private readonly errorMessage$;
     private readonly viewPortReady$;
+    /**
+     * Synchronous adoption flag. The `streamAdopted` reducer sets it BEFORE any
+     * action subscriber runs, so the connection-phase closers (which fire inside
+     * the same dispatch, e.g. `ssinfo-received` off the `ssData` state change)
+     * can read it and defer to the prefetch-timed attribution emitted by
+     * {@link emitAdoptedConnection} instead of recording the live wall-clock.
+     */
+    private readonly adopted$;
+    /** Streamer identity for the adopted signaling phase params. */
+    private readonly ssData$;
+    private readonly awsInstance$;
     private session;
     /**
      * Whether a session has already started during the current page lifetime.
@@ -1277,6 +1288,36 @@ declare class StreamStatusTelemetryService2 {
      * are derived from neighbor phases.
      */
     private emitPhaseEnded;
+    /**
+     * Emit the region / signaling / webrtc phases for an ADOPTED connection.
+     *
+     * The prefetch script established the connection in PARALLEL with page load,
+     * so the phases are positioned at their real (anchor-relative) spans — shifted
+     * LEFT to overlap the HTML-loading / route-idle rows — rather than sequentially
+     * after them. That's the whole point of the prefetch: the handshake already
+     * happened while the page was loading. Each phase ships:
+     *  - `duration` — the real sub-step time the prefetch spent.
+     *  - `spanStartMs` — anchor-relative start, so the viewer left-shifts the bar.
+     *  - `adoptionAtMs` — where Angular took over (the next phase, Unreal
+     *    communication, resumes here on the sequential timeline).
+     *  - savings params: `prefetchConnectMs` (full handshake), `prefetchSavedMs`
+     *    (done before Angular was ready), `adoptionWaitMs` (real connect→adopted
+     *    wait), `adoptionOverheadMs` (prefetch-ready → adopted gap).
+     */
+    private emitAdoptedConnection;
+    /**
+     * Emit one adopted phase positioned at its real `spanStartMs` (left-shifted
+     * to overlap page load) with its real prefetch `duration`. `prefetched`,
+     * `spanStartMs` and `adoptionAtMs` ride as top-level wire fields the viewer
+     * uses to lay the bar out; the rest become display params.
+     */
+    private emitAdoptedPhase;
+    /** Streamer identity params for the adopted signaling phase — mirrors the
+     *  `ssinfo-received` closer's shape (client / instanceName / …ssData). */
+    private adoptedSignalingParams;
+    /** Read the region-ping cache the prefetch reused (localStorage), so the
+     *  adopted region phase can still report the winning region + samples. */
+    private readRegionCache;
     private handleWindow;
     private evaluateAnomalies;
     private updateMaxFpsTarget;
@@ -2589,9 +2630,29 @@ declare const initSignalling: node_modules__ngrx_store_types_ngrx_store.ActionCr
 declare const streamAdopted: node_modules__ngrx_store_types_ngrx_store.ActionCreator<string, (props: {
     machineId: string | null;
     ssData: SignalingData | null;
+    /**
+     * `performance.now()` marks the prefetch script recorded while it
+     * established the connection (`prefetch_start` / `ws_open` / `dc_open` /
+     * `ready`), on the page navigation timeline. The telemetry service uses
+     * them to attribute the signaling / webrtc phase durations to the time the
+     * prefetch actually spent — instead of dumping the whole pre-adoption wait
+     * onto whichever phase closer happens to fire first. `null` when adopting a
+     * stream that carried no timings.
+     */
+    timings: Record<string, number> | null;
 }) => {
     machineId: string | null;
     ssData: SignalingData | null;
+    /**
+     * `performance.now()` marks the prefetch script recorded while it
+     * established the connection (`prefetch_start` / `ws_open` / `dc_open` /
+     * `ready`), on the page navigation timeline. The telemetry service uses
+     * them to attribute the signaling / webrtc phase durations to the time the
+     * prefetch actually spent — instead of dumping the whole pre-adoption wait
+     * onto whichever phase closer happens to fire first. `null` when adopting a
+     * stream that carried no timings.
+     */
+    timings: Record<string, number> | null;
 } & node_modules__ngrx_store_types_ngrx_store.Action<string>>;
 declare const startStream: node_modules__ngrx_store_types_ngrx_store.ActionCreator<string, (props: {
     config: Partial<StreamConfig>;
@@ -2810,7 +2871,6 @@ declare class UnrealEffects {
     connectToSignaling$: node_modules_rxjs_dist_types.Observable<{
         value: boolean;
     } & node_modules__ngrx_store_types_ngrx_store.Action<string>> & node_modules__ngrx_effects_types_ngrx_effects.CreateEffectMetadata;
-    regionTelemetryOnAdopt$: node_modules_rxjs_dist_types.Observable<node_modules__ngrx_store_types_ngrx_store.Action<string>> & node_modules__ngrx_effects_types_ngrx_effects.CreateEffectMetadata;
     private canPeerReconnect;
     /**
      * Either schedules the next peer-reconnect attempt or gives up with the
@@ -2827,6 +2887,7 @@ declare const unrealFeature: {
     name: "unrealFeature";
     reducer: node_modules__ngrx_store_types_ngrx_store.ActionReducer<_3dsource_angular_unreal_module.UnrealState, node_modules__ngrx_store_types_ngrx_store.Action<string>>;
     selectUnrealFeatureState: node_modules__ngrx_store_types_ngrx_store.MemoizedSelector<Record<string, any>, _3dsource_angular_unreal_module.UnrealState, (featureState: _3dsource_angular_unreal_module.UnrealState) => _3dsource_angular_unreal_module.UnrealState>;
+    selectAdopted: node_modules__ngrx_store_types_ngrx_store.MemoizedSelector<Record<string, any>, boolean, (featureState: _3dsource_angular_unreal_module.UnrealState) => boolean>;
     selectFreezeFrame: node_modules__ngrx_store_types_ngrx_store.MemoizedSelector<Record<string, any>, _3dsource_angular_unreal_module.FreezeFrameMessage, (featureState: _3dsource_angular_unreal_module.UnrealState) => _3dsource_angular_unreal_module.FreezeFrameMessage>;
     selectIsVideoPlaying: node_modules__ngrx_store_types_ngrx_store.MemoizedSelector<Record<string, any>, boolean, (featureState: _3dsource_angular_unreal_module.UnrealState) => boolean>;
     selectStatusMessage: node_modules__ngrx_store_types_ngrx_store.MemoizedSelector<Record<string, any>, string | null, (featureState: _3dsource_angular_unreal_module.UnrealState) => string | null>;
@@ -2883,6 +2944,13 @@ interface UnrealState {
     isAfkTimerVisible: boolean;
     afkCountdown: number;
     cirrusConnected: boolean;
+    /**
+     * True once a prefetched connection has been adopted (`streamAdopted`).
+     * Read synchronously by the telemetry service so the connection-phase
+     * closers know to defer to the prefetch-timed attribution instead of the
+     * live-event one. Reset on every fresh attempt / disconnect.
+     */
+    adopted: boolean;
     viewportReady: boolean;
     freezeFrameFromVideo: FreezeFrameMessage;
     freezeFrame: FreezeFrameMessage;