Updating java applet cache
Java defines two interesting type modifiers: transient and volatile.
These modifiers are used to handle somewhat specialized situations.
Also, accesses to the master variable must be executed in the precise order in which they are executed on any private copy.
Your explanation is perfectly clear and not in need of "illustrative examples"!
In particular, it succinctly makes clear that one should ALWAYS decorate an instance variable that is to be shared with "volatile". I got simple solution for my breath taking problem. It is very tedious to get all information sometimes.
The volatile modifier tells the compiler that the variable modified by volatile can be changed unexpectedly by other parts of your program.
One of these situations involves multithreaded programs.
When an instance variable is declared as transient, then its value need not persist when an object is stored.
For example: Here, if an object of type T is written to a persistent storage area, the contents of a would not be saved, but the contents of b would.