[concurrency-interest] Coordinated Runnables

Zhong Yu zhong.j.yu at gmail.com
Thu Aug 29 10:26:08 EDT 2013


Hi Alexei, if in your model one place can be connected to only one
transition, can't we model one transition with its input places as one
actor?

Zhong Yu

On Thu, Aug 29, 2013 at 7:09 AM, Alexei Kaigorodov
<alexei.kaigorodov at gmail.com> wrote:
> Package java util.concurrent provides many facilities to synchronize
> threads, but none to coordinate tasks running on a thread pool. Generally,
> using thread synchronization in tasks is undesirable, as synchronization
> blocks pooled threads and may lead to thread starvation or, if unlimited
> pool is used, leads to uncontrolled growth of the number of threads and so
> eliminating the advantages of thread pool. However, non-blocking
> synchronization facilities are essential for developing complex asynchronous
> programs.
>
> An illustrative example of how coordinated runnables can work and what
> support is required can be found at
> https://docs.google.com/document/d/1a-ycXfvVtDExDRBLKCukSjDQHlyidrVE7yV27jlEmrs
> .
>
> I also have and implementation of the proposed execution model at
> https://github.com/rfqu/df4j.
>
> I believe, for the sake of completeness, standard java libraries must
> include non-blocking sychronization facilities. Dot Net platform has Task
> Parallel Library (TPL), Groovy has GPars, and java lags behind.
>
>
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest


More information about the Concurrency-interest mailing list