Skip to content
This repository has been archived by the owner on Jan 5, 2019. It is now read-only.

Have connections on individual Threads #1

Open
ncharlton02 opened this issue Dec 24, 2017 · 2 comments
Open

Have connections on individual Threads #1

ncharlton02 opened this issue Dec 24, 2017 · 2 comments
Labels
0.3 For July 4th Update Enhancement Library

Comments

@ncharlton02
Copy link
Contributor

Currently, the Server class has every connection on its own thread. This will cause the connections to have lots of lag when we get multiple robots connecting the FMS. Each connection should have its own thread which handles communications. Then the main backend thread will handle the messages over a Thread Channel.
ncharlton02 added a commit that referenced this issue Dec 24, 2017
@ncharlton02
Remove TODO comments and convert them to Github issues (#1, #2)
40b8e7e
@ncharlton02
Copy link
Contributor Author

Should we do this on Socket stream or the connection object?

@ncharlton02
Copy link
Contributor Author

For now I don't think we need to work on this as we are getting around 5-10 ping with 4 connections which is fine

@ncharlton02 ncharlton02 added the 0.3 For July 4th Update label May 12, 2018
@ncharlton02 ncharlton02 mentioned this issue Jun 15, 2018
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
0.3 For July 4th Update Enhancement Library
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ncharlton02