mori VS react-websocket

immutable-js or mori for immutable data structures

Use persistent immutable data structures (as implemented in, for instance, mori or Immutable.js) to represent the state. As much as possible, push calculations into referentially transparent functions (i.e., input depends purely on output) which take persistent data. Write the interactions with the real world in imperative style.

Mori

Always make immutable variables. You can achieve this by having a persistence data structure using Mori or immutable.js libraries to open the features such as linked list, trees, path dealing to help with efficiency. I will not be covering how to create a persistence data structure using those libraries as it’s not the scope of this post.

from flask_socketio import SocketIO, emitapp = Flask(__name__)app.config['SECRET_KEY'] = 'secret!'socketio = SocketIO(app)... # Server functionality for receiving and storing data from elsewhere, not related to the websocket# Handle the webapp connecting to the [email protected]('connect')def test_connect(): print('someone connected to websocket') emit('responseMessage', {'data': 'Connected! ayy'})# Handle the webapp connecting to the websocket, including namespace for [email protected]('connect', namespace='/devices')def test_connect2(): print('someone connected to websocket!') emit('responseMessage', {'data': 'Connected! ayy'})# Handle the webapp sending a message to the [email protected]('message')def handle_message(): print('someone sent to the websocket')# Handle the webapp sending a message to the websocket, including namespace for [email protected]('message', namespace='/devices')def handle_message2(): print('someone sent to the websocket!')@socketio.on_error_default # handles all namespaces without an explicit error handlerdef default_error_handler(e): print('An error occured:') print(e)if __name__ == '__main__': socketio.run(app, debug=True, host='0.0.0.0') For the front end, I initially tried using a library as well. I went with react-websocket.