Re: bug in BinaryDeserializer?

On Mon, Apr 28, 2003 at 09:24:57AM -0500, [email protected] wrote:
> > 
> > Is this a bug in the (de)serialization code or is this behaviour expected?
> 
> As you say, ordinarily the deserialization methods don't need to look at 
> the contents of a deserialized object right away.  This is an exception, 
> so it suggests we need a way to specify that we need the object fully 
> initialized during deserialization, (and thus we need to serialize it so 
> that can happen).  Since its a JavaObject, we probably actually want the 
> ser/deser methods or the contract of JavaObject to hint to the 
> serialization that this needs to be enforced.
> 
Actually, I take that back, it should be done from the hashtable, say 
with a read/writeInitializedExpression or something.

	Scott



--

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+rUH9r9IW4v3mHtQRAiz9AJ9XyP5wdbdNAkBuE3qWy0uL2dfDUgCfTUxy
K1ALhGLBnrN8me3yYEg3FYs=
=wABi
-----END PGP SIGNATURE-----