Message-ID: <20468675.3975.1369413085289.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3974_1004937190.1369413085288" ------=_Part_3974_1004937190.1369413085288 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The actor support in gpars were inspired by the Actors library i= n Scala but have meanwhile gone beyond that.
Actors allow for a messa=
ging-based concurrency model, built from independent active objects that ex=
change messages and have no mutable shared state. Actors can help solve or =
avoid issues like deadlocks, livelocks or starvation, so typical for shared=
A nice wrap-up of the key concepts behind actors was written recently by Ruben Vermeersch
Actors can share a rela= tively small thread pool. This can go as far as having many concurrent acto= rs that share a single pooled thread. They avoid the threading limitations = of the JVM.
Actor code is processed in chunks separated by quiet peri= ods of waiting for new events (messages). This can be naturally modeled thr= ough continuations. As JVM doesn't support continuations directly,= they have to be simulated in the actors frameworks, which has slight impac= t on organization of the actors' code. However, the benefits in most cases = outweigh the difficulties.
example by Jordi Campos i Miralles, Departament de Matem= =C3=A0tica Aplicada i An=C3=A0lisi, MAiA Facultat de Matem=C3=A0tiques, Uni= versitat de Barcelona
For more details on Actors visit the Acto= rs section of the User Guide.
Please also see the numerous Actor = Demos.------=_Part_3974_1004937190.1369413085288--