@Zeblote I have a class, call it MonitorThing, that polls an external http service every N seconds in a background thread. I don’t expose any of the threading or http semantics to the user of the class…they just call MonitorThing::GetStatus() and get a cached value of the service’s status. So the http call can be synchronous and not lag the game, because it’s already running in a thread.
The original problem was the fact that using the async Http library inside of a thread is prone to deadlocks because it tries to schedule its delegate call on the game thread, not the original thread it was initiated from.