Workflow 0.8.1 → 0.8.2
raw patch · 3 files changed
+66/−65 lines, 3 filesPVP: major bump suggested
API removals or changes: PVP suggests a major version bump
API changes (from Hackage documentation)
- Control.Workflow: instance [overlap ok] (Monad m, Functor m) => Applicative (Workflow m)
- Control.Workflow: instance [overlap ok] (Monad m, Functor m) => Functor (Workflow m)
- Control.Workflow.Stat: instance [overlap ok] Typeable1 WFRef
+ Control.Workflow: instance [overlap ok] (Monad m, Functor m) => Applicative (WF s m)
+ Control.Workflow: instance [overlap ok] (Monad m, Functor m) => Functor (WF s m)
+ Control.Workflow.Stat: instance [overlap ok] Typeable WFRef
- Control.Workflow: delWFHistory :: Indexable a => [Char] -> a -> IO ()
+ Control.Workflow: delWFHistory :: Indexable a => String -> a -> IO ()
- Control.Workflow: delWFHistory1 :: [Char] -> IO ()
+ Control.Workflow: delWFHistory1 :: String -> IO ()
- Control.Workflow: safeFromIDyn :: (Typeable a, Serialize a) => IDynamic -> Either String a
+ Control.Workflow: safeFromIDyn :: (Typeable * a, Serialize a) => IDynamic -> Either String a
- Control.Workflow.Stat: getHeader :: STR ([Char], Int, Maybe Integer, Integer, [a], (Context, ByteString))
+ Control.Workflow.Stat: getHeader :: STR (String, Int, Maybe Integer, Integer, [t], (Context, ByteString))
- Control.Workflow.Stat: readHeader :: ByteString -> Handle -> IO (Maybe ([Char], Int, Maybe Integer, Integer, [a], (Context, ByteString)))
+ Control.Workflow.Stat: readHeader :: ByteString -> Handle -> IO (Maybe (String, Int, Maybe Integer, Integer, [t], (Context, ByteString)))
Files
- Control/Workflow.hs +2/−2
- Control/Workflow/Stat.hs +2/−2
- Workflow.cabal +62/−61
Control/Workflow.hs view
@@ -212,7 +212,7 @@ -instance (Monad m,Functor m) => Functor (Workflow m ) where +instance (Monad m,Functor m) => Functor (WF s m ) where fmap f (WF g)= WF (\s -> do (s1, x) <- g s return (s1, f x)) @@ -256,7 +256,7 @@ where plift = step -instance (Monad m, Functor m) => Applicative (Workflow m) where +instance (Monad m, Functor m) => Applicative (WF s m) where pure x= return x WF f <*> WF g= WF $ \s -> do (s1, k) <- f s
Control/Workflow/Stat.hs view
@@ -108,8 +108,8 @@ rStat= do integer integer- versions <- readp- (wfName, state, timeout, lastActive,references,cont) <- getHeader+ versions <- readp -- !> "read versions"+ (wfName, state, timeout, lastActive,references,cont) <- getHeader -- !> "read header" let self= getDBRef $ keyResource stat0{wfName= wfName}
Workflow.cabal view
@@ -1,61 +1,62 @@-name: Workflow-version: 0.8.1-cabal-version: >= 1.6-build-type: Simple-license: BSD3-license-file: LICENSE-maintainer: agocorona@gmail.com-stability: experimental-bug-reports: agocorona@gmail.com-synopsis: Workflow patterns over a monad for thread state logging & recovery-description: 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--category: Control, Workflow--author: Alberto Gómez Corona--data-dir: ""--extra-source-files: Demos/Fact.hs Demos/Inspect.hs- Demos/docAprobal.hs Demos/sequence.hs----library- build-depends: exceptions >= 0.6, RefSerialize ,- TCache , base >=4 && <5, binary , bytestring ,- containers , directory -any, extensible-exceptions ,- mtl , old-time , stm >2, vector-- exposed-modules: Control.Workflow- Control.Workflow.Configuration- Control.Workflow.Patterns- Control.Workflow.Stat- exposed: True- buildable: True- extensions: OverlappingInstances UndecidableInstances- MultiParamTypeClasses ExistentialQuantification- TypeSynonymInstances RecordWildCards DeriveDataTypeable- hs-source-dirs: .- other-modules:---source-repository head- type : git- location: https://github.com/agocorona/Workflow+ +name: Workflow +version: 0.8.2 +cabal-version: >= 1.6 +build-type: Simple +license: BSD3 +license-file: LICENSE +maintainer: agocorona@gmail.com +stability: experimental +bug-reports: agocorona@gmail.com +synopsis: Workflow patterns over a monad for thread state logging & recovery +description: 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 + +category: Control, Workflow + +author: Alberto Gómez Corona + +data-dir: "" + +extra-source-files: Demos/Fact.hs Demos/Inspect.hs + Demos/docAprobal.hs Demos/sequence.hs + + + +library + build-depends: exceptions >= 0.6, RefSerialize , + TCache , base >=4 && <5, binary , bytestring , + containers , directory -any, extensible-exceptions , + mtl , old-time , stm >2, vector + + exposed-modules: Control.Workflow + Control.Workflow.Configuration + Control.Workflow.Patterns + Control.Workflow.Stat + exposed: True + buildable: True + extensions: OverlappingInstances UndecidableInstances + MultiParamTypeClasses ExistentialQuantification + TypeSynonymInstances RecordWildCards DeriveDataTypeable + hs-source-dirs: . + other-modules: + + +source-repository head + type : git + location: https://github.com/agocorona/Workflow