Package maintainers and Hackage trustees are allowed to edit certain bits
of package metadata after a release, without uploading a new tarball.
Note that the tarball itself is never changed, just the metadata that is
stored separately. For more information about metadata revisions, please
refer to the
Hackage Metadata Revisions FAQ.
| No. |
Time |
User |
SHA256 |
| -r2 (Workflow-0.8.3-r2) |
2023-11-01T07:17:06Z |
AndreasAbel |
47824f069850bc24a3436138736f3d6b722a6b40229fc82f4dfc73babb2d5846
|
|
Changed cabal-version
from 1.6
to 1.8 Changed the library component's library dependency on 'base'
from >=4 && <5
to >=4 && <4.12 Changed the library component's library dependency on 'bytestring'
from >=0
to <0.11
|
| -r1 (Workflow-0.8.3-r1) |
2015-05-02T17:49:41Z |
HerbertValerioRiedel |
1be542eaf091e04c561a2a589f37330b0a65d6d3d5a44609c197a74e8385c64b
|
|
Changed description
from 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:
* Adaptation for MonadMask instance introduced in the package exceptions-0.6
to 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 communication
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 configuration 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:
* Adaptation for MonadMask instance introduced in the package exceptions-0.6
|
| -r0 (Workflow-0.8.3-r0) |
2015-05-01T15:57:04Z |
AlbertoCorona |
7d7d5cbe8afa76ade14ac431de727790335ceecacbd2b2fe7826a61b6c3f85a6
|
|
|