Move to using Sockets for Server/Client Communication #42

Open
opened 2023-07-22 03:43:49 -04:00 by logan · 0 comments
Owner

Replace current API method for client/server communication with sockets.

When a node starts it calls out to the server, this way communications can be opened without the client having to VPN or port forward.

When a node loses connection with the server, it should keep retrying until the server is back online. Once it's back online it will open a new socket with the server.

When the server loses connection with a node, it should assume the node went offline and should close all open connections.

All other updates to config and presets should be made through the socket connection.

Replace current API method for client/server communication with sockets. When a node starts it calls out to the server, this way communications can be opened without the client having to VPN or port forward. When a node loses connection with the server, it should keep retrying until the server is back online. Once it's back online it will open a new socket with the server. When the server loses connection with a node, it should assume the node went offline and should close all open connections. All other updates to config and presets should be made through the socket connection.
logan added this to the Full Command and Control from Server milestone 2023-07-22 03:43:49 -04:00
logan added the
core function
label 2023-07-22 03:43:49 -04:00
logan added this to the Discord Radio Bot - Command and Control project 2023-07-22 03:43:49 -04:00
logan added the
Socket Function
label 2023-07-22 15:02:23 -04:00
Sign in to join this conversation.
No description provided.