I've been pondering this recently and have come to the following conclusions: * State is expressed as a fold on a stream of events. The Event Sourcing pattern.

I've been pondering this recently and have come to the following conclusions: * State is expressed as a fold on a stream of events. The Event Sourcing pattern. * Clients send commands and receive updates to the state on separate channels. (CQRS) * Sharejs seems to be about the only thing that makes sense to manage client states. I'd quite like to build the server in Haskell as it's such a good fit for expressing folds over streams. One thing that I've not really got a handle on though is the correspondence between OT and Event sourcing... Is OT simply the operation that you use to fold the stream of events into a state or is there more to it than that? Enlightenment gratefully received!