[SOLVED] Betterway of writing java Threads

[sandeepsai39]

i asked "happens-before" question after reading java tutorial only,but i did n't get proper idea on that ,that's why i asked same question here.

[Singing Boyo]

hmm... I've never really looked into it. It's something I always recognized, and so I never looked into it deeply. However, it regards the fact that a Thread may access data that is, by the the time the access is complete, incorrect. This is due to fields being edited at the same time by different threads. A happens-before relationship is established when the programmer ensures that a field or method that is accessed by multiple Threads can only be accessed by one at a time. The most common way of doing this is through synchronization.

Fundamentally, a happens-before relationship means that one Thread will always recognize that another Thread edited the field being accessed, whether that access is achieved directly or through methods.

[sandeepsai39]

Fundamentally, a happens-before relationship means that one Thread will always recognize that another Thread edited the field being accessed, whether that access is achieved directly or through methods

Is it means one Thread actions are viewable to other Threads

[neilcoffey]

Think of "happens before" has meaning "will behave as expected if occurs in time before...". In terms of how the Java Virtual Machine is strictly defined to operate, there's a list of certain threading-related actions which are defined to have a "happens before" relationship.

But it's not necessarily the most practical way of remembering how to program correctly. The golden rule you need to keep in your head is that if data is accessed by more than one thread, you need to do something to make sure that that access is safe. That "something" could be using synchronized, volatile, final, using one of the concurrency utility classes such as ConcurrentHashMap etc etc. I'd recommend learning about these things rather than getting too bogged down in the JVM definition to start with.

The thing that generally goes wrong in threading/concurrent programming is when people try to be too clever and deliberately flout the basic rules that they know. For example, they invent some clever way to "avoid synchronization". So long as you just follow the rules rather than trying to come up with some clever way to not follow the rules, you'll generally be fine...

[sandeepsai39]

Thanks for all for your valuable sugggestions .I am sure i will come back again with another thrread bcs i have lot of questions in my mind