Hi Shawn,
On Mon, May 25, 2015 at 4:29 PM, Shawn Garner
wrote:
> The arbiter sounds like what we would need.
> Are there any activator templates or example of someone using an arbiter
> in Akka you can point me to?
> This way I could demo it to my coworker without having to write something
> fro
The arbiter sounds like what we would need.
Are there any activator templates or example of someone using an arbiter in
Akka you can point me to?
This way I could demo it to my coworker without having to write something
from scratch?
A lot of the problems at my company are cultural rather than
Hi Shawn,
The use case you're referring to (transitive ordering) I think
traditionally is accomplished in the actor model with the use of
"arbiters":
https://en.wikipedia.org/wiki/Indeterminacy_in_concurrent_computation
I.e. you need a single source of truth w.r.t. the ordering, and since
Actors a
Hi Shawn,
You need to handle such actors like a state machine, initial state will just
stash incoming messages and when its ready unstash all messages, for that Akka
has UntypedActorWithStah
HTH,
Guido.
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>>
I was talking with a coworker and he has some custom behavior he can't
understand how to do anything useful without.
He want's an tell message (a') sent from A -> C to not allow actor A to
continue until after there is confirmation that A's message is in C's
mailbox.
This way if a sends (a'') to
