Vadim Gritsenko wrote:
Is it possible to use application context to share those global variables?
It's possible, but I don't see any benefit over using the session.
Memory consumption. Several people already chimed in that they want to have "session-less" flows.
What if those variables *are* global? If they are stored in the session they become local to the current user.The intention is that they are per-user state, so storing them in the session makes sense.
See example in this thread with var role = .........ROLE;
These kind of variables are not local to the current user. You can also have some other application-wide variables.
Back to Antonio's suggestion. Can we have a configuration of the flow controller specifying where to store those global variables? Context, session, and request (that should be analogue to "no session", right?) can be possible values.
Where would you specify this, exactly?
Geoff suggested couple of places:
This seems to be a good solution too, as long as it's not once per application. It seems it would need to be on <map:flow> or <map:call>?
I think map:flow is appropriate.
Vadim
