Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How has Serialization changed in the Java 2 SE SDK, v1.3?

April 26, 2017changed Java SDK SE serialization v1.3

0

Posted

How has Serialization changed in the Java 2 SE SDK, v1.3?

1 Answer

0

Posted

Location: http://www.jguru.com/faq/view.jsp?EID=44246 Created: May 3, 2000 Modified: 2000-05-03 17:32:13.317 Author: Tim Rohaly (http://www.jguru.com/guru/viewbio.jsp?EID=10) Serialization has improved in three key ways: • Speed of reading and writing serialized objects was improved up to 40%. This also dramatically improves RMI performance. • Limit of 64K on the size of strings has been removed. This entailed changes in the serialization protocol. Older versions of the Java SDK still can’t read these long Strings, and will generate a java.io.StreamCorruptedExceptio if they encounter this new protocol. • More specific information is reported when an exception occurs during deserialization. This is important for RMI because code movement and dynamic class loading are particularly hard to debug unless specific error messages are generated.