News for hackers. Stuff that matters.

A comment on Oracle plans to dump risky Java serialization. Parent comment

Re:Oracle plans to dump risky Java serialization by _pmf_ on Monday May 28, 2018 @03:07AM (#17170991)
> The killed it in .NET Core 1.x; but brought it back in .NET Core 2.x due to back compat and interop complaints

I've been using .NET binary serialization for dirt cheap local snapshots for the purpose of undo/redo. It's perfect for this.

[ Parent | on HN ]
Re:Oracle plans to dump risky Java serialization by GordonS on Monday May 28, 2018 @06:34AM (#17171677)
There are plenty of other options though, such as JSON, MessagePack, Protocol Buffers etc. And BinaryFormatter has always performed poorly against 3rd party libs, especially other binary formatters such MessagePack
[ Parent | on HN ]
Re:Oracle plans to dump risky Java serialization by _pmf_ on Monday May 28, 2018 @06:50AM (#17171736)
Do any of these options support proper handling of cycles in the object graph out of the box?
[ Parent | on HN ]
Re:Oracle plans to dump risky Java serialization by GordonS on Monday May 28, 2018 @09:28AM (#17172259)
Yes.

Using the Newtonsoft library you can configure it using `JsonSerializerSettings.ReferenceLoopHandling`, and with with protobuf-net you set `AsReference` on your class's `ProtoContractAttribute`. I don't think MessagePack-CSharp or msgpack-cli support cyclic references tho.

[ Parent | on HN ]