why does ObjectInputStream constructor block reading a header

From: kartik (kartick_vaddadi_at_yahoo.com)
Date: 10/30/04 

Date: 29 Oct 2004 20:05:13 -0700

The ObjectInputStream constructor blocks till it reads a header from
the underlying input stream. This can cause deadlocks when you have a
pair of object streams communicating over sockets (it has happened to
me). Does anybody know why it may have been coded this way instead of
reading the header on the first call to readObject()?

-kartik

Relevant Pages