Comments on: Blocking I/O in Restrooms considered harmful to bladders. http://www.brokenbuild.com/blog/2008/01/15/blocking-io-in-restrooms-considered-harmful-to-bladders/ Databases, code and all things agile. Fri, 21 Nov 2008 09:23:41 +0000 http://wordpress.org/?v=2.6.3 By: Alex C http://www.brokenbuild.com/blog/2008/01/15/blocking-io-in-restrooms-considered-harmful-to-bladders/#comment-48107 Alex C Thu, 24 Jan 2008 15:04:43 +0000 http://www.brokenbuild.com/blog/2008/01/15/blocking-io-in-restrooms-considered-harmful-to-bladders/#comment-48107 <p>Sure! Car door handles and locks are my favorite example of a non-thread-safe component. If the passenger tries to open the door at the same moment that the driver hits the "unlock all doors" button, then the door whose handle is being lifted doesn't actually unlock. The car designers probably forgot a synchronize block.</p> <p>BTW, the urinal above is not non-blocking, it's just parallelizable up to, say, 3 peers. (Har-de-har har, get it? Peers / pee-ers? Please groan louder. Thank you.)</p> Sure! Car door handles and locks are my favorite example of a non-thread-safe component. If the passenger tries to open the door at the same moment that the driver hits the “unlock all doors” button, then the door whose handle is being lifted doesn’t actually unlock. The car designers probably forgot a synchronize block.

BTW, the urinal above is not non-blocking, it’s just parallelizable up to, say, 3 peers. (Har-de-har har, get it? Peers / pee-ers? Please groan louder. Thank you.)

]]>