RE: Misusing Flowscript Continuations

2007-04-04 Thread Warrell
I wonder if you have looked at the SCXML Apache project http://jakarta.apache.org/commons/scxml/. This offers a very robust implementation of a an FSM specified in XML. I'm thinking you could implement your persistent FSM in this and then query it from Cocoon. I might look into it myself although

Re: Misusing Flowscript Continuations

2007-04-04 Thread Torsten Curdt
On 04.04.2007, at 11:12, Warrell wrote: I wonder if you have looked at the SCXML Apache project http://jakarta.apache.org/commons/scxml/. This offers a very robust implementation of a an FSM specified in XML. *shiver* I'm thinking you could implement your persistent FSM in this and then

Re: Misusing Flowscript Continuations

2007-03-06 Thread Tobia
Dev at weitling wrote: Any idea how to misuse FlowScript is appreciated :-) I don't know if this can be considered misuse of flowscript. It's an email confirmation thingy made as a trivial state machine. The interesting part is the interaction of the step variable with the continuation. Here

Re: Misusing Flowscript Continuations

2007-03-06 Thread Dev at weitling
Hi Tobia, I don't know if this can be considered misuse of flowscript. We are at a misunderstanding now... It's not about email. It's about an object (here a question for an examination) going through a process of creation, editing, rating, translating by several users (authors, experts,

Re: Misusing Flowscript Continuations

2007-03-06 Thread Bertrand Delacretaz
On 3/6/07, Dev at weitling [EMAIL PROTECTED] wrote: ...My idea was to model that process as flow handling the state as continuation entries saved in the database. When a user has a question on his to-do-list the database-loaded continuation just continues in the flow You might be better

Re: Misusing Flowscript Continuations

2007-03-06 Thread Tobia
Dev at weitling wrote: My idea was to model that process as flow handling the state as continuation entries saved in the database. I don't think it's a good idea to save (serialized) continuation objects in a database. What happens when you restart Cocoon? What happens when you upgrade Cocoon

Re: Misusing Flowscript Continuations

2007-03-06 Thread Dev at weitling
You might be better served with a workflow engine, see http://wiki.apache.org/cocoon/Workflow for example. Looks great. I start digging thru! (Solving a problem by lavishing with solutions ;-) Thanks, Florian - To

Re: Misusing Flowscript Continuations

2007-03-06 Thread Dev at weitling
I don't think it's a good idea to save (serialized) continuation objects in a database. What happens when you restart Cocoon? What happens when you upgrade Cocoon / Rhino / whatever? Those questions have been gnawing on me, too. I'm in search of an easy way to model a state machine as

Re: Misusing Flowscript Continuations

2007-03-06 Thread Torsten Curdt
On 06.03.2007, at 14:58, Tobia wrote: Dev at weitling wrote: Any idea how to misuse FlowScript is appreciated :-) I don't know if this can be considered misuse of flowscript. It's an email confirmation thingy made as a trivial state machine. The interesting part is the interaction of the

Re: Misusing Flowscript Continuations

2007-03-06 Thread Torsten Curdt
On 06.03.2007, at 16:46, Tobia wrote: Dev at weitling wrote: My idea was to model that process as flow handling the state as continuation entries saved in the database. I don't think it's a good idea to save (serialized) continuation objects in a database. What happens when you restart

Re: Misusing Flowscript Continuations

2007-03-06 Thread Tobia
Torsten Curdt wrote: That's a misuse of continuations. Why the steps? That's what the continuation will do for you. Think outside of the state machine showPasswordForm(); sendEmail(); // now the email will have the link to the continuation showSentPage(); // execution will suspend

Re: Misusing Flowscript Continuations

2007-03-06 Thread Torsten Curdt
On 06.03.2007, at 18:32, Tobia wrote: Torsten Curdt wrote: That's a misuse of continuations. Why the steps? That's what the continuation will do for you. Think outside of the state machine showPasswordForm(); sendEmail(); // now the email will have the link to the continuation