The Workflow package

[Tags: bsd3, library]

Transparent support for interruptible computations. A workflow can be seen as a persistent thread that executes a monadic computation. Therefore, it can be used in very time consuming computations such are CPU intensive calculations or procedures that are most of the time waiting for the action of a process or an user, that are prone to comunication failures, timeouts or shutdowns. It also can be used if you like to restart your program at the point where the user left it last time . . The computation can be restarted at the interrupted point thanks to its logged state in permanent storage. The thread state is located in files by default. It can be moved and continued in another computer. Besides that, the package also provides other higher level services associated to workflows: Workflow patterns, and a general configuarion utility, workflow observation events and references to the internal state. The state can be stored maintaining memory references (using the RefSerialize package), so that it is possible to track the modifications of a big structure (for example a document) along the workflow execution.

See Control.Workflow for details

In this release: * start and startWF exception control fixed


Versions0.1, 0.2, 0.3, 0.5.5, 0.5.6, 0.5.8,,,,,,,,,,,,,,,,,,,,,,, 0.8.1, 0.8.2, 0.8.3
Change logNone available
Dependenciesbase (==4.*), binary, bytestring, containers, directory, extensible-exceptions, MonadCatchIO-mtl, mtl, old-time, RefSerialize (==0.3.1.*), stm (>2), TCache (<1.0), vector [details]
AuthorAlberto Gómez Corona
CategoryControl, Workflow
Source repositoryhead: git clone
UploadedSat Jun 15 09:40:16 UTC 2013 by AlbertoCorona
DistributionsLTSHaskell:0.8.3, NixOS:0.8.3, Stackage:0.8.3
Downloads6588 total (254 in last 30 days)
0 []
StatusDocs uploaded by user
Build status unknown [no reports yet]




Maintainers' corner

For package maintainers and hackage trustees