Akka.NET 和原始 Akka 可以使用 Remoting 通信吗？
Can Akka.NET and Original Akka communicate Using Remoting?
Akka.NET 和原始 Akka 可以使用 Remoting 通信吗？
也就是说Akka可以用来连接系统中的JVM和CLR吗？
akka.net Github https://github.com/akkadotnet/akka.net/issues/132 上的这个问题描述了这不起作用的几个原因：
1) We use different serializers for user messages, Akka uses the
default Java serializer, Akka.NET uses Json.NET. This could be solved
by using e.g. google protobuf, serializers are pluggable.
2) Helios (akka.net transport) and Netty (akka transport) are most
likely not compatible on a binary level, both do use a 4 byte length
prefix to frame messages (AFAIK, @Aaronontheweb ?) but my guess is
that they won't play nice together.
或许更根本的是：
The big issue here is this: Java is BigEndian, .NET is LittleEndian -
at least, it's LittleEndian on most Windows systems. Endianness in
.NET can vary from platform to platform, which is true for Mono too.
看来也没有太大的解决问题的欲望：
I'm wondering how useful full protocol compatibility really is. So
even with the issues you point out aside, imagine having to constantly
maintain versions that work with specific Akka versions. You never
know when something is going to change. Seems like it would be a
nightmare to maintain.
I just don't see a compelling use case for wanting to run Akka.NET and
Akka fully meshed. I would think that you normally just need to
provide some limited functionality on the other side. It can be useful
to maintain the same design pattern (actor model) across both systems,
but full compatibility I'm not so sure.
所以它不太可能很快起作用。
Akka.NET 和原始 Akka 可以使用 Remoting 通信吗？
也就是说Akka可以用来连接系统中的JVM和CLR吗？
akka.net Github https://github.com/akkadotnet/akka.net/issues/132 上的这个问题描述了这不起作用的几个原因：
1) We use different serializers for user messages, Akka uses the default Java serializer, Akka.NET uses Json.NET. This could be solved by using e.g. google protobuf, serializers are pluggable.
2) Helios (akka.net transport) and Netty (akka transport) are most likely not compatible on a binary level, both do use a 4 byte length prefix to frame messages (AFAIK, @Aaronontheweb ?) but my guess is that they won't play nice together.
或许更根本的是：
The big issue here is this: Java is BigEndian, .NET is LittleEndian - at least, it's LittleEndian on most Windows systems. Endianness in .NET can vary from platform to platform, which is true for Mono too.
看来也没有太大的解决问题的欲望：
I'm wondering how useful full protocol compatibility really is. So even with the issues you point out aside, imagine having to constantly maintain versions that work with specific Akka versions. You never know when something is going to change. Seems like it would be a nightmare to maintain.
I just don't see a compelling use case for wanting to run Akka.NET and Akka fully meshed. I would think that you normally just need to provide some limited functionality on the other side. It can be useful to maintain the same design pattern (actor model) across both systems, but full compatibility I'm not so sure.
所以它不太可能很快起作用。