You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, two libs are used on the communication part of the server:
websocketpp, used to expose websockets to the web client
seasocks, used to run a simple file server to download files and corpus
websocketpp was found and used way before the need to serve static files came. Once we needed to download archives from the web client, we found seasocks to be really simple to build and use. But it also provides a websocket interface, which can be used on the same port as the HTTP server.
This change could free a lot of resources and an exposed port used by the server. But before doing so, one must check the viability of the seasocks library on the websockets side.
The text was updated successfully, but these errors were encountered:
Right now, two libs are used on the communication part of the server:
websocketpp
, used to expose websockets to the web clientseasocks
, used to run a simple file server to download files and corpuswebsocketpp
was found and used way before the need to serve static files came. Once we needed to download archives from the web client, we foundseasocks
to be really simple to build and use. But it also provides a websocket interface, which can be used on the same port as the HTTP server.This change could free a lot of resources and an exposed port used by the server. But before doing so, one must check the viability of the
seasocks
library on the websockets side.The text was updated successfully, but these errors were encountered: