Since you can call objc code from C++, probably not.
FiveCent
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
From
Singapore
Post
Replies
Boosts
Views
Activity
And you think that running multiple requests concurrently will do that? That’s a common misconception. The goal of modern HTTP protocols (HTTP/2 and HTTP/3) is to multiplex all the requests to a specific host over a single connection [2]. So, you can dump as many HTTP requests into your NSURLSession as you like, and you’ll still only get one connection.
So what does httpMaximumConnectionsPerHost in NSURLSession actually do for HTTP/(2 or 3)? According to the documentation,
The default value is 6.
This is used for HTTP/1.1 as anything > 6 might be perceived as a DOS attack by a server.
In HTTP/2, SETTINGS_MAX_CONCURRENT_STREAMS in the "SETTINGS" frame is used to determine the maximum number of concurrent connections that can be multiplexed. Hence, it leads me to believe that this setting actually does nothing, which some people have pointed out here.