On 9/25/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
One further comment here ... this kind of state is really part of the view, not the model. Therefore, you should design it with that in mind.
An example of a general purpose approach to this is the Dialog feature of Shale ( http://shale.apache.org), or the corresponding facilities in Spring WebFlow, where the temporary state information is maintained for you, through the lifetime of a particular dialog with the user, and then thrown away for you when the dialog is completed. In essence, this behaves like a scope that is "longer than a request, but shorter than a session."
What do you thing about this?
I would tend to maintain the temporary state information in a separate model bean of some sort, explicitly designed to be Serializable, so that there would not be anything special about migrating from one server instance to another.
One further comment here ... this kind of state is really part of the view, not the model. Therefore, you should design it with that in mind.
An example of a general purpose approach to this is the Dialog feature of Shale ( http://shale.apache.org), or the corresponding facilities in Spring WebFlow, where the temporary state information is maintained for you, through the lifetime of a particular dialog with the user, and then thrown away for you when the dialog is completed. In essence, this behaves like a scope that is "longer than a request, but shorter than a session."
Regards
Ingo
Craig
Craig
