If you use a tool that automagically makes protocol out of classes it is really hard to deal with wire compatibility, giving guarantees that old messages can still be deserialized, for example on rolling upgrades, or when stored (akka-persistence) for a longer period of time. Both these aspects are important to all Akka specific messages. In addition to that the schema allows us to do optimizations we could not do without it, default cases by sending no data at all when possible for example.
If you have a use case where none of those things matters, kryo or any other schema-less can be perfectly fine. Personally I still prefer explicit protocols over implicit ones, but that might be a matter of taste. -- Johan Akka Team -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
