title: J Oliver EventStore V2.0 questions
body: <p>I am embarking upon an implementation of a project using CQRS and intend to use the J Oliver EventStore V2.0 as my persistence engine for events.</p>
  
  <p>1) In the documentation, ExampleUsage.cs uses 3 serializers in "BuildSerializer".  I presume this is just to show the flexibility of the deserialization process?</p>
  
  <p>2) In the "Restart after failure" case where some events were not dispatched I believe I need startup code that invokes GetUndispatchedCommits() and then dispatch them, correct?</p>
  
  <p>3) Again, in "ExampleUseage.cs" it would be useful if "TakeSnapshot" added the third event to the eventstore and then "LoadFromSnapShotForward" not only retrieve the most recent snapshot but also retrieved events that were post snapshot to simulate the rebuild of an aggregate.</p>
  
  <p>4) I'm failing to see the use of retaining older snapshots.  Can you give a use case where they would be useful?</p>
  
  <p>5) If I have a service that is handling receipt of commands and generation of events what is a suggested strategy for keeping track of the number of events since the last snapshot for a given aggregate.  I certainly don't want to invoke "GetStreamsToSnapshot" too often.</p>
  
  <p>6) In the SqlPersistence.SqlDialects namespace the sql statement name is "GetStreamsRequiringSnaphots" rather than "GetStreamsRequiringSnapShots"</p>