If a replica asks for a state, the DEfaultRecoverable
andDefaultSingleRecoverable might try to make the application parse a NOOP
operation that is used only within the logs of the state. Currently the demos
have a workaround this issue, but it is necessary to had code to explicitly
signal that this is not meant to be delivered.
I believe this can be done if we also log the MEssageContext objects, like it
is already being done in Durability Coordinator. If we had this longing to
DefaultRecoverable plus a new getter to indicate a NOOP, we fix 2 issues
simultaneously.
Original issue reported on code.google.com by liquidsn...@sapo.pt on 16 Jan 2015 at 8:48
Original issue reported on code.google.com by
liquidsn...@sapo.pt
on 16 Jan 2015 at 8:48