Hello, the short and sweet of it, what is the best method for threading a network manager that waits on data coming from other sources. The Jobs System, async/await, coroutine, or something else? The long of it, I'm wanting to use NetMQ (ZeroMQ) for netcode for my game as netcode for gameobjects can't handle the ship entities I am spawning that have thousands of child game objects that need to by synced between server and clients, and netcode for entities seems way too daunting as I'd have to rewrite pretty much my entire project it seems to get even simple things to work. In this case NetMQ would have a while(true) loop constantly waiting on data to arrive to act on, so the assumption is that this would need to be in a separate thread as to not interfere with the flow of normal game code. For this separate thread, what would be the "correct" method of implementation, Jobs System, async/await, coroutines, or something else? Or am I going down the wrong path all together? The next friction point would be getting the data back to the main thread, but I assume the thread safe way to do that is with Native Containers, as they, as far as I understand it, have locks and checks to make them thread safe.