Activity

Thanks for the submission, Mike. I've added Juergen, Arjen and others as watchers on this issue and slated it for the 3.2 backlog. Agreed that 3.2 is likely the right time to consider such functionality; I'll be interested to see what other users have to say about this as well. Use cases would be helpful to ensure we're all on the same page.

Chris Beams
added a comment - 01/Nov/11 6:07 PM Thanks for the submission, Mike. I've added Juergen, Arjen and others as watchers on this issue and slated it for the 3.2 backlog. Agreed that 3.2 is likely the right time to consider such functionality; I'll be interested to see what other users have to say about this as well. Use cases would be helpful to ensure we're all on the same page.

We have similar need. Our use case is simple. We are creating an aggregated resource. We need to call several underlying REST APIs and when all of the results return, we merge them to return aggregated result. We want to execute all the requests in parallel. So the ideal API would be

Lukas Krecan
added a comment - 08/Mar/12 4:16 AM We have similar need. Our use case is simple. We are creating an aggregated resource. We need to call several underlying REST APIs and when all of the results return, we merge them to return aggregated result. We want to execute all the requests in parallel. So the ideal API would be
Future result1 = execute(...);
Future result2 = execute(...);
Future result3 = execute(...);
merge(result1, result2, result3);

Lukas Krecan
added a comment - 03/Oct/12 12:01 PM I have written a quick prototype of AsyncRestTemplate https://github.com/lukas-krecan/spring-framework/commit/1f55c1b571f6c68810bf3d4582bb65da0fb4f5d8 . Basically it wraps RestTemplate , executes the corresponding method using AsyncTaskExecutor and returns Future instead of the original return value. Please let me know what you think about it. If you are interested, I will fix the documentation, formating, tests and other stuff and will issue a pull request.

Rossen Stoyanchev
added a comment - 04/Oct/12 6:14 AM Yes, that will certainly be one part of the implementation. We'll also want to support HTTP libraries that provide non-blocking support like Appache HttpComponents HttpAsyncClient.

Luciano Leggieri
added a comment - 15/Oct/13 6:53 AM Do you think it's worth to add support for https://github.com/AsyncHttpClient/async-http-client ? It's a popular framework for non-blocking connections.
I have a first draft here: https://github.com/lukiano/async-http-client-spring