Thanks for your reply Sean.
I have read about the proposed changes of the query side in akka
persistence and I think you are right regarding the use of views in this
case. I'm going to have go at using a separate read store to keep track of
the events processed as you suggested.
Rune
On Frid
Rune,
I wouldn't knock yourself out using the persistent views (as I did, even
going so far as creating dynamic views upon aggregate creation) because the
design is undergoing some big changes. In my opinion you'd be better off
having an actor listening for the events on behalf of all persisten
