我使用ws4py.websocket包创建了一个安全的websocket服务器。
javascript客户端连接到这个websocket并向它发送一些json消息。
现在,当我的js客户端关闭连接(function disconnect)时,需要大约30秒才能调用服务器的closed函数
代码如下:
服务器

class ControlWebSocket(WebSocket):

    def opened(self):
        print("Client connected")

    def closed(self, code, reason=None):
        print("Connection closed [%d]" % (code))

    def received_message(self, m):
        #some business logic using 'm'
server = make_server('', 8999, server_class=WSGIServer, handler_class=WebSocketWSGIRequestHandler, app=WebSocketWSGIApplication(handler_cls=ControlWebSocket))
server.socket = ssl.wrap_socket (server.socket, certfile='./cert.pem', keyfile='key.pem', server_side=True)
server.initialize_websockets_manager()
server.serve_forever()

顾客
ws = new WebSocket("wss://192.168.42.1:8999/");

ws.onopen = function() {
    console.log("Connected to WebSocket server");
};

ws.onmessage = function(e) {
    //some business logic using e
};

ws.onclose = function() {
    console.log("Disconnected from WebSocketServer");
};

function disconnect() {
    console.log("Disconnecting from WebSocketServer");
    ws.close();
}

有什么线索说明为什么这么长时间才结束这段关系吗?有什么方法可以更快地终止连接吗?

最佳答案

这是你的客户端问题如果您查看ws模块在最高层

const closeTimeout = 30 * 1000; // Allow 30 seconds to terminate the connection cleanly.

然后你有下面的代码
  if (!this._finalized) {
    if (this._closeFrameReceived) this._socket.end();

    //
    // Ensure that the connection is cleaned up even when the closing
    // handshake fails.
    //
    this._closeTimer = setTimeout(this._finalize, closeTimeout, true);
  }

这是为了确保连接不会在30秒前关闭,并为每一方提供足够的时间来清理连接这一次是const而不是configurable本身。但是如果你想立即终止,你可以在ws.finalize()之后加一个ws.close(),它会立即断开
const WebSocket = require('ws');
let ws = new WebSocket("wss://127.0.0.1:8999/", {
    rejectUnauthorized: false
});

ws.onopen = function() {
    console.log("Connected to WebSocket server");
};

ws.onmessage = function(e) {
    //some business logic using e
};

ws.onclose = function() {
    console.log("Disconnected from WebSocketServer");
};

function disconnect() {
    console.log("Disconnecting from WebSocketServer");
    ws.close();
    ws.finalize();
}

setTimeout(disconnect, 100)

编辑-1
在深入挖掘之后,ws4py似乎有一些与rfc6455不一致的东西。
当您从nodejs执行close时,它会发送一个\x88\x80的close帧,这表示应该关闭连接并发送一个close帧。文件ws4py/streaming.py在没有正确响应此帧时存在一些问题。它基本上期望更多的数据被读取,并被困在等待相同的数据这将导致从客户端以默认的30秒超时关闭连接。
所以这是您正在使用的python库中的一个bug。我使用NodeJS创建了一个客户机,它正常关闭。
为什么不在nodejs中使用服务器呢?在下面的链接中有一个很好的例子
https://github.com/websockets/ws/blob/master/examples/ssl.js
此处编码以供参考
'use strict';

const https = require('https');
const fs = require('fs');

const WebSocket = require('..');

const server = https.createServer({
  cert: fs.readFileSync('../test/fixtures/certificate.pem'),
  key: fs.readFileSync('../test/fixtures/key.pem')
});

const wss = new WebSocket.Server({ server });

wss.on('connection', function connection (ws) {
  ws.on('message', function message (msg) {
    console.log(msg);
  });
});

server.listen(function listening () {
  //
  // If the `rejectUnauthorized` option is not `false`, the server certificate
  // is verified against a list of well-known CAs. An 'error' event is emitted
  // if verification fails.
  //
  // The certificate used in this example is self-signed so `rejectUnauthorized`
  // is set to `false`.
  //
  const ws = new WebSocket(`wss://localhost:${server.address().port}`, {
    rejectUnauthorized: false
  });

  ws.on('open', function open () {
    ws.send('All glory to WebSockets!');
  });
});

10-06 05:23
查看更多