akka - Akka.NET 和原始 Akka 可以使用 Remoting 进行通信吗？

Question

Akka.NET 和原始 Akka 可以使用 Remoting 进行通信吗？

换句话说，Akka 可以用于连接系统中的 JVM 和 CLR 吗？

Answer 1

这个问题在 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.

因此，它不太可能很快奏效。