Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimize the REST->Socket communicator. #4

Open
binn opened this issue Nov 28, 2017 · 1 comment
Open

Optimize the REST->Socket communicator. #4

binn opened this issue Nov 28, 2017 · 1 comment

Comments

@binn
Copy link
Contributor

binn commented Nov 28, 2017

This applies to the OtakoSocket class (found within the OtakoSocket.cs file). This class is used for communication between the RESTful backend and WebSocket server.

There's an automatic failover designed for unsuccessful events and disconnection from the socket, but it's very unoptimized. The failover thread also stays running after the backend's center process is closed. (Only observed on Windows 10, while testing, but let me know if something similar can be seen on Linux).

To build just fork and go into the project folder and type

dotnet restore
dotnet run

easy.

@Greek
Copy link

Greek commented Jan 25, 2018

are we gonna do this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants