4 ms·
Erlang lacks holes in the region of mutual exclusion of an Actor making it very difficult to things like a readers/writer scheduler for a database. See the fol
by carlehewitt 8y ago
Erlang lacks holes in the region of mutual exclusion of an Actor making it very difficult to things like a readers/writer scheduler for a database.
See the following:
http://web.stanford.edu/class/ee380/Abstracts/190123.html http://web.stanford.edu/class/ee380/Abstracts/190123.html
- glockenspielen 8y agoMutual exclusion: https://en.m.wikipedia.org/wiki/Mutual_exclusion https://en.m.wikipedia.org/wiki/Mutual_exclusion Are you saying that the Erlang VM enforces mutual exclusion within its Actors, and that mutual exclusion should not be enforced within Actors?
- carlehewitt 8y agoEvery Actor has a region of mutual exclusion. However, the region of mutual exclusion can have holes so that * activities can be suspended and later resumed * other activities can use the region of mutual exclusion while a message is being processed by another Actor For example, a readers/writer scheduler for a database must be processing multiple activities concurrently, which is very difficult to implement in Erlang.