In other words, the session does not allow the websocket to reopen after it closes - the session is immediately aborted.
A way to reproduce this is with using reconnecting-websocket or partysocket.
import { newWebSocketRpcSession } from "capnweb";
import { WebSocket as ReconnectingWebsocket } from "partysocket";
const sesssion = newWebSocketRpcSession(
new ReconnectingWebsocket("ws://localhost:8001/rpc")
);
Is this intentional behaviour of the default websocket transport? If so, would a new ReconnectingWebsocket transport be acceptable or should this be left to userland? I'm not sure what your thoughts are about adding new transports to core.