Some object serialization problems for discussion(3)-ObjectInputStream

Object serialization problems about ObjectInputStream, part 1: Consider read (...) here: public int read (byte data[], int offset, int length) throws IOException { if (this.readDataFromBlock) { - if (this.blockDataPosition + length >= this.blockDataBytes){ + if (this.block

Re: Some object serialization problems for discussion(3)-ObjectInputStream

> "Bryce" == Bryce McKinlay <[EMAIL PROTECTED]> writes: Bryce> Yes, In this case I dont see why it shouldn't be done in Java Bryce> unless there is a compelling performance advantage in doing Bryce> otherwise. In fact I suspect that all of Serialization can be Bryce> implemented in pure Java,

RE: Some object serialization problems for discussion(3)-ObjectInputStream

Hi, Bryce, I heard of a pure-java implementation of java.util.zip.* named jazzlib, but I never tried it. Would you like to try it? > It should be trivial to merge the BigInteger stuff into classpath. For >java.util.zip as you know it is more > difficult for us due to the native code

Re: Some object serialization problems for discussion(3)-ObjectInputStream

"Wu, Gansha" wrote: > libgcj implements callReadObject, callWriteObject in java, but classpath >demands native to > do them; Yes, In this case I dont see why it shouldn't be done in Java unless there is a compelling performance advantage in doing otherwise. In fact I suspect that all of S