1.3 KiB
1.3 KiB
kind, description
| kind | description |
|---|---|
| upgrade-guide | Non-page Clients default to no forwarded interactions and use raw streams without browser recovery. |
Select interaction participation for non-page clients
English | 中文
Change
Non-page Connection installations default to interactions: 'none'. They do not open $events, and $on() and the generation-recovery helper $stream() are unavailable in that mode. Generated unary and raw stream methods remain usable. Browser authentication, existing browser Cookies, the shared Peer, and recovery behavior are unchanged; browsers need no reauthentication.
Migration
- Exchange the launch token at
GET /connect?token=<launch-token>&interactions=nonewith manual redirect handling. Keep the returned API Cookie in client-owned storage and use it for HTTP and the lifecycle WebSocket at the returned 302 Location. HTTP need not wait for the socket to open. - For passive streaming, call the generated raw stream method directly rather than
$stream(). After lifecycle-socket closure or Host restart, perform a new connect before retrying. - If the caller intentionally answers forwarded interactions, request
interactions=answerand install Connection with that same mode. Confirm passive callers are refused at both event endpoints while the answering caller can subscribe.