3 ms·
I would hate to see serialization go completely. It has its uses. Maybe Java should copy the attributes that the C# data contract serializer uses to mark the su
by gmueckl 8y ago
I would hate to see serialization go completely. It has its uses. Maybe Java should copy the attributes that the C# data contract serializer uses to mark the subset of classes that may appear in serialized form. It coukd be retrofitted and would be a less drastic change at the same time.
- bitmapbrother 8y agoIs it really going away, though? The article mentions that it's just being replaced with a safer implementation.
- gmueckl 8y agoI may be wrong, but to me it seems like they will replace the current implementation with something fundamentally incompatible. My impression is that dependencies like RMI will go away, too. But that would be a huge breaking change.
- bitmapbrother 8y agoSure it's going to be incompatible and break old code. The title, however, makes it seem like Oracle is getting rid of serialization when it's just replacing it with a safer method.
- gmueckl 8y agoJust for the sake of arguing semantics: "Just replacing" is incorrect in my view. The new implementation is designed specifically to not be one. It is a different mechanism mit a different interface and a different design goal.
- tannhaeuser 8y agoJava has had the "transient" keyword for that since 1.0.
- pvg 8y agoIt also didn't have serialization in 1.0 neatly avoiding the entire problem.
- tannhaeuser 8y agoYou're right, it was introduced in 1.1 (February 1997)
- skocznymroczny 8y agoAhh, the old "TempleOS is immune to <insert latest vulnerability" defense
- Pxtl 8y agoUgh, don't remind me about the data contract serializer. Silent failure for unexpected ordering of XML elements is boneheaded default behavior.