webSocketLoomJoin

Join a WebSocket session someone else is already relaying.

Call this on the device that connects out. Hand the returned loom a WebSocketAdvertisement — the URL and identity the relay published — and its us.tractat.kuilt.core.Loom.join dials it and gives you a two-peer us.tractat.kuilt.core.Seam.

This builds the same loom KtorClientLoom's constructor does. What it adds is the argument order every kuilt fabric factory shares (#1430): the fabric's own required argument first — the httpClient you own the lifecycle of — then the universal knobs, selfId then policy then dispatcher, then this fabric's remaining tuning. KtorClientLoom keeps its own older order and remains the surface for dependency injection and tests.

Where the hosting counterpart is. There is deliberately no webSocketLoomHost beside this. Hosting a WebSocket relay means mounting a route on a running server, which exists on JVM and Android only and is KtorServerLoom/KtorRoomHost's job — a different construction shape (an Application plus a path) that the convention explicitly does not try to flatten. The role split at construction is irreducible here; the convention governs the universal knobs.

One knob the convention names is deliberately absent, because this fabric does not honour it, and an argument that is accepted and then ignored is worse than one that does not exist:

• weaveTimeout — nothing in this loom puts a clock on the dial. weave calls Ktor's webSocketSession and waits as long as the httpClient waits, so the only ceiling on a rendezvous is the one the caller configured on that client (install(HttpTimeout)), not anything this factory could pass. Adding one would be new wiring rather than a forwarded knob, and it would sit alongside the client's own connect timeout with undefined precedence. Bound the dial where the dial is configured. See #1430.

policy used to be a second such omission, for a reason that has since been fixed rather than worked around: WebSocketSeam — this fabric's seam adapter — called us.tractat.kuilt.core.fabric.identified without a DeliveryPolicy, so nothing passed here could have reached the inbox. #2686 made it carry one, so the knob is real now and the argument is honoured.

Parameters