In current WebWork the main focus is on "actions".
I miss the EXPLICIT implementation of the concept "dialog".
In my view a dialog is a finite state machine implementation (FSM), an
action causes a state transition in the active state machine(s) (the (s) is
because an application will usually con
"Dort, Rob van" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, December 15, 2002 11:26 PM
Subject: [OS-webwork] Actions and Dialogs
> In current WebWork the main focus is on "actions".
>
> I miss the EXPLICIT implementation of the concept &qu
> In current WebWork the main focus is on "actions".
>
> I miss the EXPLICIT implementation of the concept "dialog".
WebWork is an engine for the controller and view parts of you app only. For
your model you have to write your own code, and in this layer you can have
your state machine if you like
In current WebWork the main focus is on "actions".
I miss the EXPLICIT implementation of the concept "dialog".
In my view a dialog is a finite state machine implementation (FSM), an
action causes a state transition in the active state machine(s) (the (s) is
because an application will usually con
