You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Min RK e15938d1a6 Backport PR #1471: Fixes for reconnecting on a flaky network ... Problem: When a client loses their websocket connection and then reconnects, this triggers the creation of new, identical zmq sockets with a collision in their routing IDENTITY. This causes messages to be lost, even though the websocket connection is established. Fix: if a duplicate connection (same session id, same kernel id) is attempted, close the stale one. My first thought was to refuse colliding connections, but for the most likely case of a flaky network where the earlier session hasn't been closed yet, this experience is quite unpleasant, ...		10 years ago
..
comm.js	Revert "Use NPM, node ES5, and browserify."	11 years ago
kernel.js	Backport PR #1471: Fixes for reconnecting on a flaky network	10 years ago
serialize.js	Revert "Use NPM, node ES5, and browserify."	11 years ago