On Friday 06 January 2006 02:07, Jonathan Locke wrote: > the constructor would still be un-threadsafe though, wouldn't it?
Constructors need to worry about synchronization on static members. The other case for synchronization concerns relating to constructors, is when the thread "leaves" the constructor to foreign classes passing itself as a reference. That way someone may pick up the object prior to the completion of the constructor and potentially introduce sync issues within the constructor. Cheers Niclas ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
