Re: bug in BinaryDeserializer?
Matthias Radestock <[email protected]>
| Newsgroups | gmane.comp.java.sisc.devel |
|---|---|
| Message-ID | <[email protected]> |
[email protected] wrote: > 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. It's the contract on the Hashtable that matters since generally it's perfectly ok to ser/deser JavaObject the way we do. What I don't understand is why the (de)serializer does what it does. Is it employing a breadth first strategy in order to avoid deep stacks? In that case having a {read/write}DirectExpression method that uses depth first instead would work. Matthias. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf