Thomas Heigl
Thomas Heigl
Could somebody take a look at this? The fix suggested by @oxc is quite trivial and prevents hitting Redis multiple times per request.
@rdlabo any chance we can get any of the proposed solutions for limited login applied to this repo?
@tinder-johnbuhanan: Can't you simply use the built-in ArraysAsListSerializer from Kryo 5? If you are on Kryo 5, you don't need any custom serializers. If you are on Kryo 4, you...
Hi @magro! kryo-serializers is still relevant for Kryo 5 because there are no built in serializers for unmodifiable and synchronized collections. Also Guava and JodaTime are still widely used. I...
@magro: Thanks a lot! What permissions do I need to perform a release? I guess you will need to add me somewhere? Is the release process the same as for...
Thanks @magro!
Kryo 5 can be used without problems. The Readme just doesn't reflect that.
@paplorinc: What kind of issue did you have? I'm using Kryo 5 and simply call: UnmodifiableCollectionsSerializer.registerSerializers(kryo); SynchronizedCollectionsSerializer.registerSerializers(kryo); The latest version of this project already depends on an old Kryo 5...
@magro: Any chance you could bump the Kryo dependency to the latest release and update the readme?
OK, that's bad. I guess this wasn't taken into account when the separate Kryo 5 artifact was created. This will be tough to fix. Since unmodifable collections are part of...