Robert,
How do you establish the order of submission? The queue will have some
order, but its a race to put things into the queue. And unless you have a
single threaded executor the order of submissions in the queue need not be
the order of execution. So I'd need to understand the ordering requirement
more fully here.
Cheers,
David Holmes
> -----Original Message-----
> From:
concurrency-interest-bounces@...
> [mailto:
concurrency-interest-bounces@...]On Behalf Of Robert
> Nicholson
> Sent: Sunday, 1 June 2008 10:51 AM
> To:
concurrency-interest@...
> Subject: [concurrency-interest] Throttling the submission
> withThreadPoolExecutor
>
>
> I would like to ask how you ensure that order of submissions is
> maintained yet still be able to throttle those submissions when using
> a bounded queue? It seems that CallerRunsPolicy allows the Task to be
> run earlier than those currently in the working queue and that in our
> particular case is unacceptable. So what is the typical approach to
> guaranteeing order at the same time still being able to throttle the
> rate of submissions. Presumably this relys on an approach whereby you
> resubmit those resubmissions upon rejection after some interval to
> increase the likehood that the resubmission itself isn't rejected?
> _______________________________________________
> Concurrency-interest mailing list
>
Concurrency-interest@...
>
http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest_______________________________________________
Concurrency-interest mailing list
Concurrency-interest@...
http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest
