On Fri, 04 Jan 2013 17:39:54 GMT, Sönke Ludwig wrote:

One way to achieve this would be to use a timer and and a signal. The requests are all run in parallel in different tasks/fibers using runTask and the original task will wait until either the timeout is reached or all requests have been answered. The only drawback is that all the late requests will continue to run after the timeout - it shouldn't have any serious impact on anything though, their connections will time out eventually or the request is finished a bit later.

A little background, we are currently using vert.x for our project, but after first online traffic tests,
we found that their client code does not satisfy our requirements.

We are considering writing a new HttpClient.

I personally find that vibe.d is more elegant (and theoretically more efficient) than vert.x/netty, so I'd like
to evaluate more and hopefully switch to vibe.d when it becomes more stable and we get more understanding to it.

I'll have to persuade my colleagues for switching to D though, which is not an easy task (because we are in Java world).

Best Regards

Puming