This is related to my first question regarding remote deployment protobuf message. The DaemonMsgCreateData has a PropsData, which in turn holds a list of args that is needed in order to create the actor instance on the remote node. This is accomplished using two repeated fields, "args" and "classes". Which makes up the serialized data for each arg and the fqcn of each arg. This differs from the design of for example "SerializedMessage" , which has a payload "message" and an int "serializerId" and a "messageManifest" Is there any reason why this distinction is made? Wouldn't it be more consistent with the overall API design if the args had a repeated message similar to "SerializedMessage" ? I'm not saying this is a bug nor that it affects any functionallity, I just found it somewhat odd. How is "null" handled if used in this arg list? is null a special type in Scala and the fqcn will be of the special null type? (assuming that you have an actor that can take null for some ctor argument that is..) //Roger
-- >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
