Завантаження документації...
Підготовка контенту платформи Ring
Підготовка контенту платформи Ring
Підготовка контенту платформи Ring
Підготовка контенту платформи Ring
Concepts, value, and typical clone scenarios — less code.
Concepts, value, and typical clone scenarios — less code.
Concepts, value, and typical clone scenarios — less code.
TunnelProvider (in app-client-shell.tsx) owns the shared WSS/SSE connection and channel-subscription-registry. Tunnel consumers — including CreditBalanceProvider and GlobalTunnelListeners — must mount inside TunnelProvider. Feature hooks such as useSync and useUnreadCount should run once inside NotificationProvider — nav widgets consume useNotificationContext(), not duplicate useUnreadCount() calls.
Ring Platform delivers realtime updates through Tunnel Protocol:
lib/tunnel/hub/) — server-side broker; SSE, native WSS, poll queues, channel subscriptions, offline per-user queueserver.ts) — Next.js handler + attachTunnelWss when RING_DEPLOY_TARGET is k8s or self-hostedlib/tunnel/tunnel-timing.ts priority/deferred routes (Tunnel protocol — timing)lib/discovery/sync-discovery.ts publishes opportunity:* and entity:* on topic channels after CRUD (Discovery mutation sync)When publishToUserTunnel runs with no live socket, InMemoryTunnelHub queues the message (publisher logs at console.debug, not an error). On connect:
app/api/tunnel/sse/route.ts drains via hub.drainUserQueueForSse(userId)lib/tunnel/native-ws/attach.ts drains via hub.drainUserQueue(userId) immediately after { op: 'auth_ok' } (parity with SSE)Boot-race messages (e.g. device telemetry during auth-grace) are delivered on the first transport handshake, not the next page load.
Routes, auth frames, priority timing, HTTP dedup hooks, and alpha limitations.
In-app alerts, preferences, and FCM push when the tab is closed.
Provider matrix and subscription dedup backlog.
TunnelProvider defers connect briefly after auth so HTTP ingest (analytics device registration, initial REST) can complete first. Priority routes — including /admin and nested /admin/* — get faster auto-connect via matchesRoutePrefix() in lib/tunnel/tunnel-timing.ts (prefix match, not exact pathname string).
Full route tables, env overrides, and boot-race SSOT: Tunnel protocol.
| Feature | Server publish | Client subscribe |
|---|---|---|
| Notifications | publishToUserTunnel → notifications:unread | NotificationProvider → useNotificationContext() |
| Credit balance | publishToUserTunnel → credit:balance | CreditBalanceProvider → useCreditBalanceContext() (bootstrap REST dedup + tunnel push) |
| Account status | publishToUserTunnel → account:status | GlobalTunnelListeners → AccountStatusTunnelListener |
| Vendor sidebar gate | — (HTTP only) | useVendorStatus() → GET /api/vendor/status (30s TTL, single-flight) |
| Chat | publishToChannel → conversation:${id} | hooks/use-messaging.ts → useTunnelChannel |
| Discovery | syncDiscovery → opportunities / entities | Topic channel subscriptions |
| Matcher |
See Tunnel protocol for API routes, RING_DEPLOY_TARGET, channel patterns, and alpha limitations.
TunnelProvider (in app-client-shell.tsx) owns the shared WSS/SSE connection and channel-subscription-registry. Tunnel consumers — including CreditBalanceProvider and GlobalTunnelListeners — must mount inside TunnelProvider. Feature hooks such as useSync and useUnreadCount should run once inside NotificationProvider — nav widgets consume useNotificationContext(), not duplicate useUnreadCount() calls.
Ring Platform delivers realtime updates through Tunnel Protocol:
lib/tunnel/hub/) — server-side broker; SSE, native WSS, poll queues, channel subscriptions, offline per-user queueserver.ts) — Next.js handler + attachTunnelWss when RING_DEPLOY_TARGET is k8s or self-hostedlib/tunnel/tunnel-timing.ts priority/deferred routes (Tunnel protocol — timing)lib/discovery/sync-discovery.ts publishes opportunity:* and entity:* on topic channels after CRUD (Discovery mutation sync)When publishToUserTunnel runs with no live socket, InMemoryTunnelHub queues the message (publisher logs at console.debug, not an error). On connect:
app/api/tunnel/sse/route.ts drains via hub.drainUserQueueForSse(userId)lib/tunnel/native-ws/attach.ts drains via hub.drainUserQueue(userId) immediately after { op: 'auth_ok' } (parity with SSE)Boot-race messages (e.g. device telemetry during auth-grace) are delivered on the first transport handshake, not the next page load.
Routes, auth frames, priority timing, HTTP dedup hooks, and alpha limitations.
In-app alerts, preferences, and FCM push when the tab is closed.
Provider matrix and subscription dedup backlog.
TunnelProvider defers connect briefly after auth so HTTP ingest (analytics device registration, initial REST) can complete first. Priority routes — including /admin and nested /admin/* — get faster auto-connect via matchesRoutePrefix() in lib/tunnel/tunnel-timing.ts (prefix match, not exact pathname string).
Full route tables, env overrides, and boot-race SSOT: Tunnel protocol.
| Feature | Server publish | Client subscribe |
|---|---|---|
| Notifications | publishToUserTunnel → notifications:unread | NotificationProvider → useNotificationContext() |
| Credit balance | publishToUserTunnel → credit:balance | CreditBalanceProvider → useCreditBalanceContext() (bootstrap REST dedup + tunnel push) |
| Account status | publishToUserTunnel → account:status | GlobalTunnelListeners → AccountStatusTunnelListener |
| Vendor sidebar gate | — (HTTP only) | useVendorStatus() → GET /api/vendor/status (30s TTL, single-flight) |
| Chat | publishToChannel → conversation:${id} | hooks/use-messaging.ts → useTunnelChannel |
| Discovery | syncDiscovery → opportunities / entities | Topic channel subscriptions |
| Matcher |
See Tunnel protocol for API routes, RING_DEPLOY_TARGET, channel patterns, and alpha limitations.
TunnelProvider (in app-client-shell.tsx) owns the shared WSS/SSE connection and channel-subscription-registry. Tunnel consumers — including CreditBalanceProvider and GlobalTunnelListeners — must mount inside TunnelProvider. Feature hooks such as useSync and useUnreadCount should run once inside NotificationProvider — nav widgets consume useNotificationContext(), not duplicate useUnreadCount() calls.
Ring Platform delivers realtime updates through Tunnel Protocol:
lib/tunnel/hub/) — server-side broker; SSE, native WSS, poll queues, channel subscriptions, offline per-user queueserver.ts) — Next.js handler + attachTunnelWss when RING_DEPLOY_TARGET is k8s or self-hostedlib/tunnel/tunnel-timing.ts priority/deferred routes (Tunnel protocol — timing)lib/discovery/sync-discovery.ts publishes opportunity:* and entity:* on topic channels after CRUD (Discovery mutation sync)When publishToUserTunnel runs with no live socket, InMemoryTunnelHub queues the message (publisher logs at console.debug, not an error). On connect:
app/api/tunnel/sse/route.ts drains via hub.drainUserQueueForSse(userId)lib/tunnel/native-ws/attach.ts drains via hub.drainUserQueue(userId) immediately after { op: 'auth_ok' } (parity with SSE)Boot-race messages (e.g. device telemetry during auth-grace) are delivered on the first transport handshake, not the next page load.
Routes, auth frames, priority timing, HTTP dedup hooks, and alpha limitations.
In-app alerts, preferences, and FCM push when the tab is closed.
Provider matrix and subscription dedup backlog.
TunnelProvider defers connect briefly after auth so HTTP ingest (analytics device registration, initial REST) can complete first. Priority routes — including /admin and nested /admin/* — get faster auto-connect via matchesRoutePrefix() in lib/tunnel/tunnel-timing.ts (prefix match, not exact pathname string).
Full route tables, env overrides, and boot-race SSOT: Tunnel protocol.
| Feature | Server publish | Client subscribe |
|---|---|---|
| Notifications | publishToUserTunnel → notifications:unread | NotificationProvider → useNotificationContext() |
| Credit balance | publishToUserTunnel → credit:balance | CreditBalanceProvider → useCreditBalanceContext() (bootstrap REST dedup + tunnel push) |
| Account status | publishToUserTunnel → account:status | GlobalTunnelListeners → AccountStatusTunnelListener |
| Vendor sidebar gate | — (HTTP only) | useVendorStatus() → GET /api/vendor/status (30s TTL, single-flight) |
| Chat | publishToChannel → conversation:${id} | hooks/use-messaging.ts → useTunnelChannel |
| Discovery | syncDiscovery → opportunities / entities | Topic channel subscriptions |
| Matcher |
See Tunnel protocol for API routes, RING_DEPLOY_TARGET, channel patterns, and alpha limitations.
publishToChannel → matcher |
| Admin/matcher UI |
| Collaboration (flagged) | collab:${id} binary CRDT frames | useCollaboration (requires WSS) |
publishToChannel → matcher |
| Admin/matcher UI |
| Collaboration (flagged) | collab:${id} binary CRDT frames | useCollaboration (requires WSS) |
publishToChannel → matcher |
| Admin/matcher UI |
| Collaboration (flagged) | collab:${id} binary CRDT frames | useCollaboration (requires WSS) |