Remove dead code

Signed-off-by: David Scott <dave.scott@eu.citrix.com>
Remove dead code

Signed-off-by: David Scott <dave.scott@eu.citrix.com>
Remove dead code

Signed-off-by: David Scott <dave.scott@eu.citrix.com>
Remove dead code

Signed-off-by: David Scott <dave.scott@eu.citrix.com>
Separate the notion of 'are side-effects visible' from 'transaction id'

We want to be able to make snapshots where no side-effects are visible
without having to physically allocate a transaction id, since allocating
ids is persisted and therefore (a) is expensive; and (b) infects
everything with the Lwt type.

Signed-off-by: David Scott <dave.scott@eu.citrix.com>
Tie side-effect visibility to 'immediate' mode

If we are in immediate mode (ie not a transaction), then side-effects
should be visible per-request. If we are in a transaction then we
don't need to compute side-effects because they'll be generated
by the operation replay.

Signed-off-by: David Scott <dave.scott@eu.citrix.com>
Incremental commit

Signed-off-by: David Scott <dave.scott@eu.citrix.com>
server: persist the next transaction id with every connection

Signed-off-by: David Scott <dave.scott@eu.citrix.com>
Merge pull request #31 from djs55/irminsule

Persist the next transaction id per connection