well, we do a lot of iterations. anytime formcomponent.isvalid() is called
we iterate over messages to see if there are any for that component. in my
apps that is called a couple of times per formcomponent per request. i went
with copyonwrite because the iterator isnt synced at all. we dont
selectively remove messages anywhere, so iterator.remove() not being
supported is not a big deal for me.
but of course if you profile it and get a better performance with something
else feel free to change it, i just went with whatever i thought was going
to give the best performance without doing any testing.
-igor
On 3/31/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> copy on write has the advantage when it comes to iterating over the
list.
Only a real advantage when there would be many threads/ many reads,
and adding is more expensive with this list. I would be surprised if
this list gives a better performance. But we can benchmark it. Another
disadvantage is that the Iterator of that list doesn't allow remove.
Eelco
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
