Actors are objects that are scheduled on Kernel threads using ForkJoin Pool?
That's how they're implemented yeah - tasks submitted to a pool.
But that misses all the things which make the model useful: isolation and location transparency (the most important one!).
So you don't care if an actor is on the same node or not, API does not change, and "fits" as it's messaging and not RPC style which hides the fact that things are remote.
On 31 March 2017 at 12:53:32, kant kodali (kant...@gmail.com) wrote: