happstack-state: Event-based distributed state.
Unplug your machine and restart and have your app recover to exactly where it left off. Happstack-State spares you the need to deal with all the marshalling, consistency, and configuration headache that you would have if you used an external DBMS for this purpose. Its component model makes it easy to compose big applications from smaller reliable parts. Use event subscription to trigger IO actions and support comet-style or irc-bot applications.
|Versions [faq]||0.1, 0.2.1, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.4.1, 0.5.0, 0.5.0.2, 0.5.0.3, 0.5.0.4, 6.0.0, 6.1.0, 6.1.1, 6.1.2, 6.1.3, 6.1.4|
|Dependencies||base (<5), bencode (>=0.5), binary, bytestring, containers, directory, extensible-exceptions, filepath, happstack-data (>=6.0.1 && <6.1), happstack-util (==6.0.*), hS3 (>=0.5.1 && <0.6), hslogger (>=1.0.2), HUnit, mtl (>=1.1 && <2.1), network, old-time, process, QuickCheck (==2.*), random, SHA (>=1.4.0 && <2), stm (>=126.96.36.199), syb, template-haskell, unix [details]|
|Author||Happstack team, HAppS LLC|
|Maintainer||Happstack team <email@example.com>|
|Category||Web, Distributed Computing|
|Source repo||head: darcs get http://patch-tag.com/r/mae/happstack (happstack-state)|
|Uploaded||by JeremyShaw at Thu Feb 16 17:17:05 UTC 2012|
|Downloads||7912 total (240 in the last 30 days)|
|Rating||(no votes yet) [estimated by rule of succession]|
Docs uploaded by user
Build status unknown [no reports yet]
Build the testsuite, and include the tests in the library
Enable state replication through a central serialization service.
Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info
For package maintainers and hackage trustees