Advanced C# TCP Socket Server
Budget: $30 – $250 USD
I’m looking for an experienced C# engineer to build a robust TCP SocketServer that can seamlessly switch between data-streaming sessions and classic request-response traffic. The server must accept both persistent, long-lived connections and quick, non-persistent ones while staying responsive and memory-safe. No encryption layer is needed—raw TCP is sufficient.
What I expect:
• .NET 6/7 compatible solution using async/await and efficient I/O completion.
• Configurable listener port, connection pool limits, and idle timeouts.
• Separate, easily extendable handlers for streaming versus request-response clients so I can plug in custom logic later.
• Clean resource management: graceful shutdown, reconnection support, and protection against socket leaks.
• Structured, timestamped logging for connect/disconnect, errors, and throughput metrics.
• Lightweight test harness or demo client to prove simultaneous persistent and non-persistent connections under load.
• Clear README explaining setup, configuration options, and extension points.
If you’ve delivered high-performance servers before, tell me about it and outline your proposed architecture and timeline. I’m ready to move quickly once I see the right approach.
What I expect:
• .NET 6/7 compatible solution using async/await and efficient I/O completion.
• Configurable listener port, connection pool limits, and idle timeouts.
• Separate, easily extendable handlers for streaming versus request-response clients so I can plug in custom logic later.
• Clean resource management: graceful shutdown, reconnection support, and protection against socket leaks.
• Structured, timestamped logging for connect/disconnect, errors, and throughput metrics.
• Lightweight test harness or demo client to prove simultaneous persistent and non-persistent connections under load.
• Clear README explaining setup, configuration options, and extension points.
If you’ve delivered high-performance servers before, tell me about it and outline your proposed architecture and timeline. I’m ready to move quickly once I see the right approach.