Kristian Marinkovic wrote:
hi davor,
Hi,
Sorry I jump in the thread,
you're right... "flash" will be an excpetion :)... the problem is that if
you use components (libraries) of other teams or third party components that
persist values in the session you still want to be able to use it in a
conversation without changing the component.
But in library, components just use the default persistence strategy. If
a strategy is specified, it should be for a meaningful reason. Perhaps
they have define there own strategy.
So I think that you should just give the possibility to change the
default strategy, not impose it. Moreover, libraries may evolve to use
your strategy with their constrains - nobody better that the dev of a
component know what may break with a modification.
making it easy to use for developers is also a goal.
That's a good goal :) (I'm a dev after all, and a lazy one ;) Just
remember that there is no free lunch, and be careful if you attempt to
interpret there will.
--
Francois Armand
Etudes & Développements J2EE
Groupe Linagora - http://www.linagora.com
Tél.: +33 (0)1 58 18 68 28
-----------
InterLDAP - http://interldap.org
FederID - http://www.federid.org/
Open Source identities management and federation
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
