A DESCRIPTION OF THE PROBLEM :
With a language with so much built in support for threading, it is a shame that the API documentation does not clearly indicate which routines are not thread safe.

Without definitive indications in the reference documentation, we are left with a sprinkling of notes in the API which idicate some support or lack of support of thread safety. Usually there is no comment and the developer has to guess as to whether or not a class/method is thread safe.



EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Each class/method have an annotation which indicates consistantly whether or not it is thread (un)safe.

Perhaps enforce a convetions where thread safety is assumed and only thread unsafe classes are marked as such (or vice versa).

Consider using a small graphic indicator whic his consistantl and easy to spot.
ACTUAL -
No consistant method of indicating thread safety.

URL OF FAULTY DOCUMENTATION :
Everywhere