Re: [akka-user] akka cluster + kryo

Thanks for the great tip. Now my config contains the following. And the warning messages disappeared. serialization-bindings { "java.io.Serializable" = none "java.lang.String" = kryo "java.lang.Boolean" = kryo //All messages that are sent around in the application.

Re: [akka-user] My initial impressions of akka.typed design.

My first impulse is to see if the need for down casts can be designed away. This would remove the contention between trying to enforce certain implementation details while simultaneously hiding those same implementation details from the user. However I am not familiar enough with the design

Re: [akka-user] akka cluster + kryo

I would not encourage setting scala.Product or java.lang.Object as kryo serialized - pick specific classes (this is also for security reasons actually). Or create a marker type that you’d include in your messages that are to be serialized using kryo and use that. Sure you can use Artery if you

[akka-user] akka cluster + kryo

Hello there, I am building a micro-service that uses akka-cluster. I am running into an issue with serialization. I am using akka 2.4.16 and scala 2.11. These warnings have started to come when I switched from default java-serialization to kryo. I am using

Re: [akka-user] My initial impressions of akka.typed design.

On Sat, Aug 26, 2017 at 8:10 PM, Roland Kuhn wrote: > Hi Sean, > > removing the self-type would not help: its function is only to ensure that > every ActorRef also has an appropriate implementation, basically proving > that the down-cast that is used in many places in the