Why isn't Object.notify() a synchronized method? (original) (raw)
Ulf Zibis Ulf.Zibis at CoSoCo.de
Thu May 28 16:08:55 UTC 2015
- Previous message: RFR: 8081392: getNodeValue should return NULL value for Element nodes
- Next message: Why isn't Object.notify() a synchronized method?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi all,
in the Javadoc of notify(), notifyAll() and wait(...) I read, that this methods should only be used with synchronisation on it's instance. So I'm wondering, why they don't have the synchronized modifier out of the box in Object class.
Also I think, the following note should be moved from wait(long,int) to wait(long): /The current thread must own this object's monitor. The thread releases ownership of this monitor and waits until either of the following two conditions has occurred:// /
- /Another thread notifies threads waiting on this object's monitor to wake up either through a call to the notify method or the notifyAll method./
- /The timeout period, specified by timeout milliseconds plus nanos nanoseconds arguments, has elapsed. /
Cheers,
Ulf
- Previous message: RFR: 8081392: getNodeValue should return NULL value for Element nodes
- Next message: Why isn't Object.notify() a synchronized method?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]