[Haskell-cafe] ANNOUNCE: MFlow 0.2
Alberto G. Corona
agocorona at gmail.com
Fri Jan 18 16:09:11 CET 2013
I will paste the rest of the blog entry:
[Continue from the first message]
Statefulness means that the flow of execution is right in front of the eyes
of the programmer, rather that in the spaghetti code of the event-handling
model, the goto of the XXI century. it also means that the entire session
is in a procedure, so the session data need no trickery.
But, like in the stateless case, any page in the flow could have a direct
Event sourcing in combination with statefulness means automatic logging of
all the events and automatic recovery of the execution state of the server
procedure and its data, thanks to the Workflow monad
So the server procedure can be stopped after timeout and restarted by the
application server when the user invokes it. The programmer can determine
the timeout and for how long the state is stored.
Back button management: the flow of execution can run
the back button is pressed . Thanks to a monad transformer. In
combination with event sourcing, this means automatic rollback of user
session data. So if the user want to undo his last item in the shopping
cart, he only has to press the back button.
It is made of self contained pieces called widgets, made around the formlet
concept, so they compose gracefully with applicative operators and other
extra operators. A MFlow widget is more like the widgets of XWindows,
ASP.NET or JavaServer Faces: they have their own HTML formatting, their own
behaviours and interact with the server via AJAX, they execute actions when
activated and they return statically typed data. They declare their
required scripts, CSS links and server procedures in the form of
requirements to the requirement service. They include the server and client
code in the same piece of text. Being self contained and typed, they can be
shared and plugged with a minimum of configuration and instructions.
The URL links are also widgets or elements of widgets and return data to
the same flow, so no spaguetty event handling occur, unless the programmer
need out-of-flow links.
This versions <http://haskell-web.blogspot.com.es/2013/01/now-example-of-use-of-active-widget.html>includes
active widgets with server-side controls for creating them .
wai-warp, blaze-html, xhtml, HSP, hack.
Persistence and transactions:
Global data can be transacted with any kind of persistence framework. MFlow
internally uses TCache , which provides with persistent STM references
(DBRefs). Their serialization can be configured. For rapid prototyping,
they have default persistence in files. Just add a Read-Show or a Binary
instance for your data and you can have a persistent, transactional DBRef
to it. Use them like you use TVars. TCache can index text and register
fields. It has a simple query language. Data can be accessed by key or by
any indexed field.
The human mind learn by examples. There is a online
some of the features that you can play with and you can download the code
2013/1/18 Ertugrul Söylemez <es at ertes.de>
> Heinrich Apfelmus <apfelmus at quantentunnel.de> wrote:
> > For some reason, your blog posts are not displayed in my browser
> > (Chrome). I block all cookies and I'm using adblock, though.
> Not to be or to be and (not to be or to be and (not to be or to be and
> (not to be or to be and ... that is the list monad.
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Haskell-Cafe