And here is another question regarding channel and command sourcing Processor.
My understanding is this, when a event is received by Processor: 1) persist the event 2) handle the event 3) call event.confirm() In case something wrong in step 2, channel will attempt to redeliver the same message to Processor, then step 1 will happen again, this means the same message is journaled twice. Based on current implementation, it's not a problem as journaling twice actually end up with the same message. But why not merge 1 and 3 so once a channel-delivered-persistent event is received and journaled by Processor, the confirm() is done automatically? Of course, this requires we to distinguishi a Persistent message and a channel-delivered-persistent message. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/groups/opt_out.
