Hi evan,
Yes that could be one solution. Part of the problem is when you initiate an HTTP request with our http_client, there isn't one task that represents and holds the whole operation. Depending on the API we build on we could quickly asynchronously initiate the request using API's asynchrony model. In the case of WinHTTP for example this is done through callbacks. This means new requests can be started up.
It would be possible there to be a throttling feature on the http_client itself, in the http_client_config perhaps. That would limit the number of active requests at one time. If this might be valuable you could open a feature request. The implementation probably would be doing something similar to what you are on top of the http_client.
Steve
Yes that could be one solution. Part of the problem is when you initiate an HTTP request with our http_client, there isn't one task that represents and holds the whole operation. Depending on the API we build on we could quickly asynchronously initiate the request using API's asynchrony model. In the case of WinHTTP for example this is done through callbacks. This means new requests can be started up.
It would be possible there to be a throttling feature on the http_client itself, in the http_client_config perhaps. That would limit the number of active requests at one time. If this might be valuable you could open a feature request. The implementation probably would be doing something similar to what you are on top of the http_client.
Steve