Hi,
Am 02.05.2014 10:35, schrieb Jochen Kemnade:
Am 24.04.2014 13:53, schrieb Jochen Kemnade:
But, to lessen the effect, couldn't we check if the attribute is
immutable and downgrade the write lock in that case?
or maybe we should just add a symbol to toggle support for persisting
mutable values in the session, defaulting to true of course.
Then we'd have the problem of knowing which classes are immutable. We
could easily solve this via a service though. Something along the lines of
contributeImmutableClasses(Configuration<Class> c){
c.add(String.class);
c.add(Integer.class);
// and then, in a custom module
c.add(MyCustomImmutableClass.class);
}
I just re-discovered the ImmutableSessionPersistedObject annotation.
Maybe we can leverage that?
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
