On 9/1/05, Craig McClanahan <[EMAIL PROTECTED]> wrote:

> 
> It's like the difference between reusing common code by refactoring it 
> into a separate method, and calling it, versus reusing common code by 
> cut-n-paste. I prefer the former :-). Incidentally, this aspect of dialog's 
> design came straight from Spring WebFlow, which draws the same sort of 
> distinction (although they manage per-webflow state quite a lot 
> differently).
> 

Of course, right after I pressed Send I thought of an even clearer way to 
look at it ... the state object of a subdialog is like the local variables 
stack of a method call that is currently in progress. It's contents are 
visible *within* that subdialog/method, but not outside.

Craig

Reply via email to