Currently both a sync (blocking) and an async (non-blocking) HTTP client is used, but we should be able to consolidate this. The reason for this currently is that all the setup happens on the main thread when starting the application and only when starting actix-web, we jump into an async world. It'd probably be nice to start in an async world from the beginning, but that would require some plumbing.
Currently both a sync (blocking) and an async (non-blocking) HTTP client is used, but we should be able to consolidate this. The reason for this currently is that all the setup happens on the main thread when starting the application and only when starting
actix-web, we jump into an async world. It'd probably be nice to start in an async world from the beginning, but that would require some plumbing.