Turn it to multi threaded

[marnelle1]

Hey! :)
Can you help please, how can I turn Networking Part 1 example to the multi threaded?
Thanks and sorry for my English!

[Luaancz]

Hi :)

It's already multi-threaded. Don't be confused by the lack of any explicit threads - the sample uses IOCP and TPL/async for handling multiple concurrent connections. There's no reason to occupy a thread when you have no CPU work to do :)

[marnelle1]

Hi! 😊 Thanks for the answer. Server works like a charm, but sometimes ESTABLISHED connection appears and server stop working ☹ I tested it before, and server stands when there is 100+ connection. От: Luaancz Отправлено: 4 февраля 2019 г. в 15:07 Кому: Luaancz/Networking Копия: nagibator96; Author Тема: Re: [Luaancz/Networking] Turn it to multi threaded (#2) Hi :) It's already multi-threaded. Don't be confused by the lack of any explicit threads - the sample uses IOCP and TPL/async for handling multiple concurrent connections. There's no reason to occupy a thread when you have no CPU work to do :) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Luaancz]

Keep in mind that there's no error handling in the sample code - you need graceful handling for all sorts of errors. The sample only manages non-exceptional TCP states. Accepting connections is only done on a single thread, so if you get a lot of connection requests at the same time (and require more than a trivial amount of time for processing new connections), you could run into the connection limit on the TCP socket (impossible with the default configuration unless you have a lot of network adapters :)), or run into connection timeouts. If you spend significant amounts of time processing a new connection, you might want to explicitly schedule that with Task.Run (or, if possible, use asynchronous operations instead of synchronous for whatever is taking the time).