For the model change recording (which btw only happens when you replace
a model) and detachable behaviour support, you could also wrap your
models in another model, that dispatches the recording and detaching.
But... if the models are not detachable and you don't replace your
models, you'll be fine without.
Actually, clustering will work allright, as Wicket also clusteres the
instance variables.
Eelco
frank bengtsson wrote:
OK, but both situations are not an issue for me in this case, since this is
pretty much a one pager and i don't live in a clustered environment :)
/Frank B.
On Monday 11 July 2005 22:07, Eelco Hillenius wrote:
You're right. Another disadvantage I didn't think about is that
detachable models won't be attached.
Eelco
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
