A two-phase commit Monad:https://gist.github.com/johnynek/6473724 …
-
-
-
Replying to @peterseibel
@peterseibel whoops… indeed a bug in the Map transaction: https://gist.github.com/johnynek/6479546/revisions …2 replies 0 retweets 0 likes -
Replying to @posco
@posco@peterseibel next, implement vector clocks, and compare the approaches.1 reply 0 retweets 0 likes -
Replying to @avibryant
@avibryant@peterseibel actually thinking about something like Transaction monad for storehaus-transact. Probably need 3 phase. thoughts?4 replies 0 retweets 1 like -
Replying to @posco
@posco@peterseibel though I realize that doesn't help for multi-key transactions. Is that a use case you're seeing a need for?1 reply 0 retweets 0 likes -
Replying to @avibryant
@avibryant@peterseibel exactly. That and composing across stores.1 reply 0 retweets 0 likes -
Replying to @posco
@posco@peterseibel sounds like that'll end up with horrific availability properties. Sure you need cross-store consistency?1 reply 0 retweets 0 likes -
Replying to @avibryant
@avibryant@peterseibel Dude, I'm just building Monads over here. I don't *need* anything…2 replies 3 retweets 11 likes
@posco @peterseibel Dr. Boykin in a nutshell, folks.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.