However, besides state synchronization is under development, state
persistence in MFlow is optional, by using the workflow monad instead of
the IO monad. See for example this:
http://mflowdemo.herokuapp.com/shop
2013/7/10 Alberto G. Corona
> My plan is to synchronize MFlow servers using cl
I factored out the submit buttons.
Now the three text boxes appear in succession above a unique button below.
http://mflowdemo.herokuapp.com/noscript/fviewmonad
This is the new code:
sumWidget= pageFlow "sum" $ do
n ← (do
n1 ← p << "Enter first number" ++> getInt Noth
My plan is to synchronize MFlow servers using cloud Haskell since the state
serialization is small. I´m working on it. However continuation based
frameworks can not synchronize state. There is "swarm" in scala that
generate portable continuations but this is not used in the context of web
applica
Here are some common-lisp web frameworks using continuations:
http://common-lisp.net/project/cl-weblocks/
http://common-lisp.net/project/ucw/features.html
What always worried me with these frameworks is how they could be made
robust in case of failures. Storing all state in a database backend of
Thanks Adrian. The racket people where pioneers in this idea I think.
There is another web framework in Ocaml, Osigen that it is also
continuation based. MFlow is not continuation-based but it also define the
navigation as a sequence. But only Seaside (and now MFlow) supports many
flows in the sam
Oh how nice!
I have been looking at MFlow a lot lately and I think it's got something
quite special that Yesod, Happstack, etc don't seem to have, at least, not
as far as I know. I mean, look at this:
sumWidget= pageFlow "sum" $ do
n1 <- p << "Enter first number" ++> getInt Nothing <**
sub
The third version of MFlow is out.
http://hackage.haskell.org/package/MFlow
MFlow is an all-heterodox web application framework, but very haskellish.
Now MFlow support restful URLs. It is the first stateful web framework to
my knowledge that supports it. The type safe routes are implicitly
expr
