Can Akka.NET and Original Akka communicate Using Remoting? -


can akka.net , original akka communicate using remoting?

in other words can akka used connect jvm , clr in system?

this issue on akka.net github https://github.com/akkadotnet/akka.net/issues/132 describes several reasons why doesn't work:

1) use different serializers user messages, akka uses default java serializer, akka.net uses json.net. solved using e.g. google protobuf, serializers pluggable.

2) helios (akka.net transport) , netty (akka transport) not compatible on binary level, both use 4 byte length prefix frame messages (afaik, @aaronontheweb ?) guess won't play nice together.

and perhaps more fundamentally:

the big issue here this: java bigendian, .net littleendian - @ least, it's littleendian on windows systems. endianness in .net can vary platform platform, true mono too.

it appears there not appetite solving issues:

i'm wondering how useful full protocol compatibility is. issues point out aside, imagine having maintain versions work specific akka versions. never know when going change. seems nightmare maintain.

i don't see compelling use case wanting run akka.net , akka meshed. think need provide limited functionality on other side. can useful maintain same design pattern (actor model) across both systems, full compatibility i'm not sure.

so unlikely work time soon.


Comments

Popular posts from this blog

get url and add instance to a model with prefilled foreign key :django admin -

css - Make div keyboard-scrollable in jQuery Mobile? -

ruby on rails - Seeing duplicate requests handled with Unicorn -