Thanks a lot for all your help on this.  I think I got this nailed.

The BackoffSupervisor is sufficient, if not a little goofy to deal with.

I am thinking that it would be better to create a supervisor strategy to 
emulate the backoff.  I am unclear as to why Akka didn't make this out of 
the box?

The advantage using *restart* instead of *Terminate -- then -- Start* is 
that the messages that come in can still be handled properly with stash if 
so desired.  If you terminate, messages that have not yet been received get 
lost to dead letters.

Either way, will need to create some trait that makes this simpler to deal 
with

Thanks again, I will update the gist once my solution is ironed out a 
little more.  Need to take a break and relax some brain cells now :)

-- 
>>>>>>>>>>      Read the docs: http://akka.io/docs/
>>>>>>>>>>      Check the FAQ: 
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>>      Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to