Hello,
I was looking to use durable mailboxes in a new akka project. Looking
through the documentation, it appears these have been dropped in favour of
akka-persistence.
I took a look into the akka-persistence documentation and from what I can
gather the goal of the project is to store process
Hi Logan,
I took a look into the akka-persistence documentation and from what I can
> gather the goal of the project is to store processed messages so that an
> actor's state can be rebuilt upon an actor's restart, while I'd like to
> store unprocessed messages so they can be processed upon an ac
The big difference is that when using akka-persistence the messages are not
stored immediately when placed in the mailbox. When you receive the
Persistent message in the Processor you know that it has been stored. The
sender can let go of the responsibility when it has received an explicit
acknowle
Great, thanks guys for pointing me in the right direction!
On Monday, March 24, 2014 10:53:23 AM UTC-4, Patrik Nordwall wrote:
>
> The big difference is that when using akka-persistence the messages are
> not stored immediately when placed in the mailbox. When you receive the
> Persistent messag
The main difference I see with the change from a DurableMailbox to using a
PersistentChannel/AtLeastOnceDelivery is the former seems "pull" based
while the latter is "push". Is this the case? I'm curious if there's a way
I can essentially implement a durable mailbox based on the Persistence
fra
Hello Jeff,
Basically I want to pile a bunch of messages into this mailbox and have the
> actor process them when it "can" with a producer timeout restriction. I
> know this is related to the Reactive Stream stuff, but I'm interested in
> something near term and deciding if I should implement a Du