Add API for skipping items in a KV store enumerator
Test the FastForward implementation
Implement the FastForward() call in the memory store
Very slow implementation of the FastForward operation. I think a way to pass through the Azure continuation token would work better :-/
Add a paging results enumerator interface so we can break up things like user events into pages.
Remove yesterdays paging system. It can't be made to be efficient with Azure.
Alternative paging interface, using a token system.

Hm, one issue here is that this means passing the TableContinuationToken value from Azure to the user, and it's not clear if this would reveal something that should be left private. (The offset system is simpler but not supported by Azure tables)
Sample implementation for the in-memory key/value store
Add a test for the paging enumeration
Change the paging test so that it regenerates the enumeration each time (an important requirement of the paging system)
Start work on a page object for the Azure table store, change to using a task-based mechanism for retrieving the contents
Initial implementation of the Azure segmented page
Add some trace messages when KV store commits process a lot of records or take a long time
Continuation token should be null if segmentToken is null
For some reason, the first result is coming out with a null/null json and key
Improve diagnostic information
Fix test so that it stops when the next page token is null instead of retrieving an endless supply of items
Add an interface for iterating over results divided into pages
Switch the user query to use a paging system
Fix the tests so that they use the new paging system for users