Thomas Heigl

@Mr14huashao: I'm currently trying to stabilize Kryo 5.0.0 and will merge only bug fix PRs in the near future. Let's revisit this after Kryo 5.0.1 has been released.

@xuedonglxd: Thanks for your PR! The PR itself is good, but as I said in the ticket, I'm not sure this is a widely useful feature. It would be possible...

@lifeinwild: Thanks for the PR! Your solution is interesting, but I don't think it's generic enough to be included as an additional class resolver in Kryo. Users have to be...

@maxisvest: If you want to get this merged, please provide a testcase that demonstrates what you are trying to achieve with your change.

@maxisvest: Thank you! I tried your test-case against the current master and it does not throw any exceptions in my case. Could this somehow depend on the JDK vendor and...

@maxisvest: We first need a test-case that can reliably replicate the issue. Please merge the current master into your branch and make sure that your test-case really fails. Currently, I...

@maxisvest: Thanks. I can now reproduce your issue and I think I understand what's going on: When chunked encoding is enabled and Kryo encounters an unknown class, it skips the...

Hi @RuedigerMoeller! Did you find any time to work on the JDK9 migration? My project uses your great library and we are planning to move to JDK11. FST is the...

Quick update: 1. I added the following serializers to Kryo. These serializers are not registered by default (because of backwards compatibility), but can be registered as needed: - `java.net.URI` -...

@leonchen83: I would not consider serializing exceptions a typical use-case for Kryo, so I'm against adding exception serializers to Kryo itself. You have two options: 1. Write your own serializer...