|
From: James E. <jam...@gm...> - 2005-04-01 15:59:34
|
Not sure why this didn't come through...size? I see it and another post from Rob in the archive...just never got them (checked another developer too). If this is a duplicate for some, I apologize. ----- What about an implementation that would 'do what is best'. Save to the session if it already exists, serialize to the request if not. Then have a custom tag to spit out the flow info in the form. The tag would pull the serialized flow info from the request (if it exists) and add a new hidden input field for it (_flowInstance or something)...otherwise if a session exists and the info is on the session it would spit out what is expected now (the _* hidden fields). At the beginning of a request, it would look to see if the serialized param (_flowInstance) is on the request first...if so, deserialize. If not, see if a session exists and pull from the session using _* params. If you have a truly complex object graph, set a 'requiresSession' boolean to true (defaults to false)...although I would think it best to try and keep it as simple as possible when going in the session. With this approach your not doing more than you need (when a session does exist), and (as a bonus) you can have flows that are used by non-session visitors and with-session users, and the impl would 'do what is best' in both situations. James |