On 8/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Personally, I don't like the idea of the framework itself relying on heavy use of the HttpSession and "hiding" it in this way. There are many cases when you want to avoid use of HttpSession for scalability reasons (there's that word ;) ).
Using session for one er... flash of moment to save/restore data is not going to ruin the scalability. Anyway, this feature will be documented as one that sparingly uses session and automatically cleans it up after a roundrip.
I like how currently WebWork/Struts 2.0 makes it difficult to get to
the raw HttpServletRequest or HttpSession... Struts 1 exposes enough HTTP-related stuff already for me to worry whether I expose some more.
That said, I might be missing the problem you are trying to solve. Is it just about abstraction of the HttpSession? Supporting Workflows?
No, this has nothing to abstracting HttpSession or supporting workflows. Like I mentioned in another reply, seems that I chose bad name that confuse people. I should either borrow Antonio's "Click" or Tapestry's/Stripes' "Flash" or just call it "Survivor scope" because this is nothing more than regular request scoped data surviving after one roundtrip. That is it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
