rtc.io-server 1.1.0 → 1.2.0

package/README.md

@@ -21,12 +21,9 @@ server.on("connection", (socket) => {
     socket.to(roomId).emit("#rtcio:init-offer", { source: socket.id });
   });
 
-  socket.on("disconnecting", () => {
-    socket.rooms.forEach((roomId) => {
-      if (roomId === socket.id) return;
-      socket.to(roomId).emit("user-disconnected", { id: socket.id });
-    });
-  });
+  // No `disconnecting` handler needed for peer cleanup — the rtc.io-server
+  // core emits `#rtcio:peer-left` automatically. Add one only if you have
+  // app-level cleanup (presence rosters, room password registries, etc.).
 });
 
 server.listen(3001);
@@ -34,7 +31,12 @@ server.listen(3001);
 
 ## What this server does
 
-The rtc.io client multiplexes all WebRTC signaling (offers, answers, ICE candidates, stream metadata) into a single `#rtcio:message` event. This server registers a default handler for that event and relays it to the addressed peer (`socket.to(target).emit(...)`). Everything else — room management, app-level events, presence — is **your** code.
+The rtc.io client multiplexes all WebRTC signaling (offers, answers, ICE candidates, stream metadata) into a single `#rtcio:message` event. This server registers default handlers that:
+
+1. Relay `#rtcio:message` envelopes to the addressed peer (`socket.to(target).emit(...)`).
+2. Emit a `#rtcio:peer-left` notification to a leaving socket's rooms on `disconnecting`, so existing peers can short-circuit ICE consent-freshness (~30 s) when a tab closes. The client treats this as a hint that's cross-checked against the local WebRTC state; it never tears down a healthy P2P call on the basis of a signaling-only event. See the [signaling protocol](https://docs.rtcio.dev/docs/server/protocol#rtciopeer-left) for the full contract.
+
+Everything else — room management, app-level events, presence — is **your** code.
 
 ### What you implement
 

package/dist/lib/defaulthandlers.js

@@ -7,6 +7,19 @@ const events_1 = require("./events");
 function rtcMessageHandler(socket, data) {
     socket.to(data.target).emit(events_1.RtcioEvents.MESSAGE, data);
 }
+// Fast-path "this socket is leaving" notification. Without it, peers have to
+// wait on ICE consent freshness (~30 s, RFC 7675) to declare a vanished peer
+// dead. With it, peers can confirm against their own WebRTC layer and tear
+// down the matching RTCPeerConnection in a couple of seconds.
+function rtcDisconnectingHandler(socket) {
+    const ownId = socket.id;
+    socket.rooms.forEach((roomId) => {
+        if (roomId === ownId)
+            return;
+        socket.to(roomId).emit(events_1.RtcioEvents.PEER_LEFT, { id: ownId });
+    });
+}
 function addDefaultListeners(socket) {
     socket.on(events_1.RtcioEvents.MESSAGE, (data) => rtcMessageHandler(socket, data));
+    socket.on("disconnecting", () => rtcDisconnectingHandler(socket));
 }

package/dist/lib/events.d.ts

@@ -5,4 +5,5 @@ export declare const RtcioEvents: {
     readonly MESSAGE: "#rtcio:message";
     readonly STREAM_META: "#rtcio:stream-meta";
     readonly INIT_OFFER: "#rtcio:init-offer";
+    readonly PEER_LEFT: "#rtcio:peer-left";
 };

package/dist/lib/events.js

@@ -8,4 +8,8 @@ exports.RtcioEvents = {
     MESSAGE: "#rtcio:message",
     STREAM_META: "#rtcio:stream-meta",
     INIT_OFFER: "#rtcio:init-offer",
+    // Server → client. Fan out to a leaving socket's rooms so existing peers
+    // can tear down their RTCPeerConnection immediately instead of waiting
+    // on ICE consent-freshness (~30 s) to declare the peer dead.
+    PEER_LEFT: "#rtcio:peer-left",
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rtc.io-server",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "description": "Signaling server for the rtc.io WebRTC client. Built on socket.io.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",