Actor Model

From Adam Colton
Revision as of 17:49, 21 September 2018 by Adamcolton (talk | contribs) (Created page with "I'm looking at the actor model and it seems interesting, but a little problematic because it's too recursive. I like this; an actor has 3 properties * Storage * Processing * ...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

I'm looking at the actor model and it seems interesting, but a little problematic because it's too recursive.

I like this; an actor has 3 properties

  • Storage
  • Processing
  • Communication

but I don't like the Communication model. Instead, a sort of Object with handlers seems good. But then there's the problem of what is communicated. I like the idea of messages being separate entities. So a message is storage and processing, but no communication. However, following the Rust model, when you send a message, you lose access to it, it is not shared.

One model has it that after sending a message, you can send any number of responses. I'm not sure I like this. Even the concept of a response gets complicated.

Questions

  • How does an actor stop?