On Fri, 12 Aug 2005 12:57:37 -0700, Igor Vaynberg <[EMAIL PROTECTED]>
wrote:
Explain the benefits of your approach as opposed to the current
implementation - I cant think of any off the top of my head.
Because you can use any object not just a string. This means you can
provide optimized item removal (lets call it oir) also to things like
wicket.examples.guestbook.Comment objects ( return new EqualsModel(ob,ob)
). I do not know an easy way to create a string id for this not db held
objects. Or in case a particular object is contained double in the
iterator you can turn of oir for just this particular item new Model(ob).
new Model(ob) gives you always an indeed unique id.
As far as collections go, performance wise I think you would be better
off
transforming it to a list first or to an array and writing an
ArrayAdapter.
Assuming your collection interface isnt backed by a dynamic source this
should work ok.
Performance wise you are right. The difference is with new
List(colleciton) the Model reflects a snapshot not the actual maybe
changing collection.
Christian
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
