[
https://issues.apache.org/jira/browse/DBUTILS-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114698#comment-13114698
]
Simone Tripodi commented on DBUTILS-78:
---------------------------------------
Thanks a lot for your prompt help William, very appreciated! :)
I proposed to use {{ExecutorService}} due to my not big experience with
concurrent APIs, and just reading basic javadoc I found that
{{ExecutorService}} is the more primitive element to run {{Callable}}s.
So apologize for having reopened the issue, I thought that just providing
{{ExecutorService}} would reduce code redundancies.
Anyway, since you submitted the initial patch (I guess you had a usecase for
having submitted it), if you can confirm that the new version of
{{AsyncQueryRunner}} would be really useful, I would be pleased to apply it.
Many thanks in advance!
Simo
> Add asynchronous batch, query, and update calls
> -----------------------------------------------
>
> Key: DBUTILS-78
> URL: https://issues.apache.org/jira/browse/DBUTILS-78
> Project: Commons DbUtils
> Issue Type: New Feature
> Reporter: William R. Speirs
> Priority: Minor
> Fix For: 1.4
>
> Attachments: 08_16_2011.diff, AsyncQueryRunner.java,
> AsyncQueryRunnerTest.java, DBUTILS-78_Future.patch,
> DBUTILS-78_Future_v2.patch, async.diff, pom.diff
>
>
> I propose a new QueryRunner class, AsyncQueryRunner, which changes the return
> type of batch, query, and update methods. Instead of returning their
> respective return types, the methods would return a RunnableFuture. This
> would allow callers to either execute the RunnableFuture in a thread or via
> an CompletionService like the ExecutorCompletionService.
> I have attached a first cut at this class.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
