Write multiclient server C# app with websockets
Budget: €8 – €30 EUR
A fully working websockets multiclient server written in C#.NET Framework has to be delivered.
Both code for client and server is necessary.
Requirements:
- DO NOT use websocket-sharp library, as I already have it working, and it's bugged.
- Code must be maintaned VERY simple, no big hardcoding or anything like that.
- Code must be 100% commented on every functions and adaptable to my needs.
- The client and server MUST be written in C# .NET and must be fully compatible with Windows 7.
What is needed:
Client side:
- The client must connect to the server at a specificed IP on specified port using entirely websockets.
- Connection must be maintaned ALWAYS open for as long as the client is open and working.
- If the client disconnects for network failure, packet drops, etc, then it must reconnect to the server and resume its work from where it has stopped.
- If the client is unable to reconnect after X attempts, then it should close and restart.
Server side:
- The server must handle multi-clients connecting and manage them all.
- Connections must be ALWAYS kept open unless told otherwise from server or client.
Connection side:
- Packets transfer containing simple commands in text form must be fully working.
You kinda can refer to it, as a very simple multi-client chat, the function is the same, even if the end-purpose is not a chat.
Both code for client and server is necessary.
Requirements:
- DO NOT use websocket-sharp library, as I already have it working, and it's bugged.
- Code must be maintaned VERY simple, no big hardcoding or anything like that.
- Code must be 100% commented on every functions and adaptable to my needs.
- The client and server MUST be written in C# .NET and must be fully compatible with Windows 7.
What is needed:
Client side:
- The client must connect to the server at a specificed IP on specified port using entirely websockets.
- Connection must be maintaned ALWAYS open for as long as the client is open and working.
- If the client disconnects for network failure, packet drops, etc, then it must reconnect to the server and resume its work from where it has stopped.
- If the client is unable to reconnect after X attempts, then it should close and restart.
Server side:
- The server must handle multi-clients connecting and manage them all.
- Connections must be ALWAYS kept open unless told otherwise from server or client.
Connection side:
- Packets transfer containing simple commands in text form must be fully working.
You kinda can refer to it, as a very simple multi-client chat, the function is the same, even if the end-purpose is not a chat.