By vroosha
via soa.sys-con.com
Published: May 24 2007 / 14:44
![]() | |
| HTML5 Canvas | |
| Written by: Simon Sarris | |
| Featured Refcardz: Top Refcardz: | |
| 150+ Refcardz Available · Get them all | |
By vroosha
via soa.sys-con.com
Published: May 24 2007 / 14:44
Comments
kunnar replied ago:
Too simple questions.
cwilkes replied ago:
Any site that has an ad with audio turned on immediately gets a thumbs down
vroosha replied ago:
sorry, i didn't even know that ad was there ;) firefox rulez ))
in86835 replied ago:
Q2 Answer has confused grammar, so maybe part wrong.
Q3 Answer is only half right.
synchronized blocks are not for saving time they are for locking a specified object (which maybe a class), so that one thread owns that object while executing inside the block, they can be less efficient and less safe that synchronized methods. You can even have nested synchronized blocks for different objects, but that can be an invitation for Thread deadlocks and maybe a sign of poor coding practice.
Q19 Answer did not mention the new advice from Sun advice that active Swing and AWT objects like JFrame, JWindow, Frame, Window etc. must only be created and access on the GUI Event Thread, even if not visible or enabled.
Voters For This Link (14)
Voters Against This Link (2)