Comments on Thoughts on Java, Java EE and web services development: Do your Iterators always fail-fast?

The survey is good. Thanks for news. To protect yo...

2011-07-22T21:09:31.602+05:30

The survey is good. Thanks for news. To protect yourself from future losses try compare homeowners insurance quotes by zip code to save more on home insurance policies.

Hello! You may probably be very curious to know ho...

2010-01-21T12:30:32.242+05:30

Hello!
You may probably be very curious to know how one can manage to receive high yields on investments.
There is no initial capital needed.
You may commense to get income with a sum that usually is spent
for daily food, that's 20-100 dollars.
I have been participating in one project for several years,
and I'll be glad to let you know my secrets at my blog.

Please visit my pages and send me private message to get the info.

P.S. I earn 1000-2000 per day now.

http://theinvestblog.com [url=http://theinvestblog.com]Online Investment Blog[/url]

Unsynchronized Collection don't need to gua...

2009-11-15T01:21:42.288+05:30
Unsynchronized Collection don't need to guard for concurrent threads: they are not thread-safe anyway.

True, but their iterator operations claim to throw an exception in case of modification. So its a kind of optimistic approach taken by the iterators. And that's fail-fast

Synchronized Collections update modCount consistently (all operations are synchronized) and the field doesn't need to be volatile.

No, even in the case of Synchronized collections only the add, remove, clear operations are synchronized. The iterator operations are not synchronized, So there would be visibility issues with the value of the modCount field. The thread that does the iterator operations might not work with the updated value of the modCount field.

The mechanism isn't primarily useful for concu...

2009-11-13T22:50:38.036+05:30
The mechanism isn't primarily useful for concurrent threads, but for nested calls:

for (Object o : list) {
...
list.remove(0);
...
}

Unsynchronized Collection don't need to guard for concurrent threads: they are not thread-safe anyway. Synchronized Collections update modCount consistently (all operations are synchronized) and the field doesn't need to be volatile.

Yeah, the point here is you should not be relying ...

2009-11-13T20:17:24.335+05:30
Yeah, the point here is you should not be relying on ConcurrentModificationException in your code.

If the iterator is certainly going to fail a littl...

2009-11-13T20:10:06.775+05:30
If the iterator is certainly going to fail a little later in a some few cases, I can't see why this is an issue. Its OK imo to treat failfast as a soft constraint.