3 ms·
Technically speaking, an Actor does not do a "return" for a request it has received. Instead, the Actor sends a 1-way message to the customer Actor that it r
by ProfHewitt 5y ago
Technically speaking, an Actor does not do a "return" for a
request it has received. Instead, the Actor sends a 1-way
message to the customer Actor that it received with the
request. Actors operate concurrently, which is different
from the object-oriented programming beginning with Simula.
- mpweiher 5y agoExactly. From TFA: "With those more general semantics, "^" might also be used to send back results to the sender of an asynchronous message, which is obviously quite different from a "return"."
- ProfHewitt 5y agoTechnically, speaking the response does not go to the sender of the request. Instead, the response goes to the customer that was received along with the request. For example, tail recursion makes of the ability to specific a customer along with a request. An Actor never knows where the request came from. Of course, the request my be signed to designate accountability for the request.
- mpweiher 5y agoa) Technically TFA never mentions the word "actor" so your mincing such fine meat regarding the exact wording of definitions in actors is utterly irrelevant. b) sender / "customer" / whatever. Whoever gets marked as the "receiver of results". From TFA: "I've already taken that and generalised it to mean "send result", using it in filter definitions, where "^" means "send a result to the next filter in the pipeline"