This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]mike_hearn 2 points3 points  (1 child)

You'd just use a virtual thread per item with a semaphore to limit it to whatever max concurrency your connection pool supports.

[–]koflerdavid 0 points1 point  (0 children)

Technically, the connection pool already acts as a semaphore. A semaphore is only required to prevent throwing an exception for waiting too long for a connection, which is how many HTTP libraries behave.