Reactive Application Development by Duncan K. DeVore Sean Walsh Brian Hanafee

Author:Duncan K. DeVore, Sean Walsh, Brian Hanafee
Language: eng
Format: mobi, epub
Publisher: Manning Publications
Published: 2018-06-06T13:36:38.597000+00:00

Instead of functions named changeAltitude() or changeSpeed(), you use message handlers within the actor.

We contend that modeling the domain independent of actors and then wrapping that domain within the actor is a waste of time, because we consider actors to be an extension of Scala or Java, so we assume that this architecture will have no other implementation of Aircraft. Follow your own heart, however, and do what feels right in your own designs.

The next section shows an Aircraft actor that communicates by using the Aircraft protocol for messaging. Because Aircraft is an actor, each message is a one-way communication, and each message is handled in the order received. The actor stores current state in memory, and each message received results in a modified replacement of that state.

5.2.2. The actor

The Akka actor encapsulates all behavior of the aircraft and does so with messaging rather than traditional function calls:

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.