OBScore VS socket.io-client

Комментарии радуют https://github.com/FunctionDJ/OBScore/issues/33

i didn't

from cmath import log from flask import Flask, render_template, request from flask_socketio import SocketIO, emit import json # https://flask-socketio.readthedocs.io/en/latest/ # https://github.com/socketio/socket.io-client app = Flask(__name__) app.config[ 'SECRET_KEY' ] = 'jsbcfsbfjefebw237u3gdbdc' socketio = SocketIO( app ) @app.route('/c') def hello(): return render_template( 'chat2.html' ) def messageRecived(): print( 'message was received!!!' ) @socketio.on( 'my event' ) def handle_my_custom_event( json ): print( 'recived my event: ' + str(json)) print(json) socketio.emit( 'my response', json, callback=messageRecived ) return json data = handle_my_custom_event() def creatlog(data): with open ('chat.json', 'w') as chat: json.dump(json) if __name__ == '__main__': socketio.run( app, debug = True )

Socket.IO’s primary use, however, is for facilitating real-time, bidirectional, and event-based communication between the browser and the server. Like ws, Socket.IO has a Node.js server and a JavaScript client library.

> Conversely, if the client does not receive a PING packet within `pingInterval + pingTimeout`, it will consider that the connection is closed.

Indeed looks like a solid way to solve the client-side recognition of a broken connection!

--

That said, I'm a little confused because I cannot find any mention of `pingTimeout` in their JS client [0], and `pingInterval` is only mentioned in an implementation of a test server [1]. I wonder if I'm looking at the wrong thing.

[0]: https://github.com/socketio/socket.io-client/search?q=pingti...