Adamcolton at 17:53, 21 September 2018

2018-09-21T17:53:00Z

← Older revision		Revision as of 17:53, 21 September 2018
Line 9:		Line 9:

	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.		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.

			Another issue is that communication is complicated and this covers it up. There needs to be a way for any message to send itself over any channel.
			* passing reference in same program
			* socket
			* file
			* internet

	Questions		Questions
	* How does an actor stop?		* How does an actor stop?

Adamcolton: 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 * ..."

2018-09-21T17:49:31Z

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 * ..."

New page

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?

Actor Model - Revision history

Adamcolton at 17:53, 21 September 2018

Adamcolton: 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 * ..."