[Seaside] WATask, or almost.

[Sebastian Sastre]

> 
> Well, but perhaps I'm thinking it wrong, but what I want is 
> some sort of "going backward" in the task.
> 
> In this case this is simple, but what if I have several steps?
> 
> And the model has to be valid only in this lifecycle, once 
> the task is done, it must be discarded.
> 

I think Continuations should take care of that for you. That is if you are
going backwards with the back button. No matter how much steps back you need
to go back, there is a continuation with the state (unless a transaction is
in the usage path).

If you want to go backwards as a function from other than the user agent's
back button, then I think you can use the continuation solution anyway by
figuring out a way your application to press it internally for him.

Did I understand right your request?

	saludetes,

Sebastian

> Saludos.
> 
> 
> --
> Esteban A. Maringolo
> eMaringolo at gmail.com
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside