We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Based on the team members discussion we have to implement the protocol to client - server communication.
This issue scope is to create a logic that identify the cases below and call a class responsible for that logic.
This issue scope doesn't cover implement all those cases logic.
The issues for implement the cases logic are: Case1: #16 Case2: #11 Case3: #12 Case4: #13 Case5: #14 Case6: #15
Case 1 - new user ask to connect to the server:
Case 2 - notification that new user connects to the server:
Case 3 - send message:
Case 4 - receive message:
Case 5 - notification that user disconnects:
Case 6 - keep alive notice:
The text was updated successfully, but these errors were encountered:
jeffhsta
No branches or pull requests
Based on the team members discussion we have to implement the protocol to client - server communication.
This issue scope is to create a logic that identify the cases below and call a class responsible for that logic.
This issue scope doesn't cover implement all those cases logic.
The issues for implement the cases logic are:
Case1: #16
Case2: #11
Case3: #12
Case4: #13
Case5: #14
Case6: #15
Protocol cases:
Case 1 - new user ask to connect to the server:
Case 2 - notification that new user connects to the server:
Case 3 - send message:
Case 4 - receive message:
Case 5 - notification that user disconnects:
Case 6 - keep alive notice:
The text was updated successfully, but these errors were encountered: