Why not call them custom scopes and link it into to contexts where
appropriate. That way you could name your scope and if it doesn't exist,
create it. Then you could have generic methods to handle all sorts of
scopes at once with generic methods like:
addScope("request").setAttribute(name, object);
addScope("session").setAttribute(name, object);
addScope("single").setAttribute(name, object);
addScope("someDialog").setAttribute(name, object);
Where a scope is created if the name doesn't already exist. Except that in
the "request" or "session" names, it automatically hooks into those scopes
for consistency. And for the Stripes equivalent "Flash" scope just call it
"single" scope or "next" scope. Basically that means you can name dialogs
of your choice plus have multiple ones. If they are linked to the Session
context then they'll auto-expire if left too long. Plus, we could add
something that enables scopes for a maximum number of requests (via a filter
perhaps) if that is a requirement, allowing a sort of auto-flush for these
potentially expired less-than-session scopes.
Regards,
David
-----Original Message-----
From: Adam Hardy [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 22, 2006 5:09 PM
To: Struts Users Mailing List
Subject: Re: FlashScope: anyone has a better name?
FlashScope definitely smells of Macromedia.
Spring Webflow has several scopes in the virtual scope-scape between request
scope and session scope, called ConversationScope and FlowScope.
Perhaps they are more to your taste?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
