On 7/28/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote: > There should be set of policies. For example, if you navigate to an > action which is not part of any subsession (or scenario, I like this > word), do you trash all existing scenarios or you keep them?
If you look at Spring Web Flow, you would see that they allow to define huge app-sized flows and subflows. This is madness, and I do not favor this. I think it is much easier not to have a flow at all, and instead to define single-level peer components (resources, actions, scenarios, whatever you call them). If you need a wizard, make it one action. The idea of subflows is do you allow certain set of actions in certain state or not. "State" is the keyword. If state is used uniformly in application, subflows would not be needed, just set or clear the state. Right... Essentially, flow with sublows is a hierarchical state. I guess I need to think of something generic app-wide state management. Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
