These are chat archives for akkadotnet/akka.net

28th
Nov 2015
Bartosz Sypytkowski
@Horusiath
Nov 28 2015 10:44
@cconstantin I don't think so, Akka.Persistence is build for eventsourcing as primary state persistence technique, as it's the most reliable in distributed, error-prone environments. If you can store only current state, it's trivial to do this by yourself, but there are some things to keep in mind i.e. how will you prevent state loss in case of outage.
Daniel Ferreira Monteiro Alves
@danfma
Nov 28 2015 12:38
hello guys!!
Do someone know if is possible to use some specific protocol, or a way to implement one, in a matter that makes the Java version compatible with the .NET one?
Bartosz Sypytkowski
@Horusiath
Nov 28 2015 17:46
@danfma right now it's not possible as transport layer itself is not compatible between Java and .NET version. This hopefully will change in the future.
Daniel Ferreira Monteiro Alves
@danfma
Nov 28 2015 18:38
But can I implement a new transport layer over the two implementations? Something json-based.
Sorry, I just want to know if I implement a transport layer for .net and the compatible one for Java, will the two clients be possible to communicate?
I did not dive into the source code of the akka yet.
Bartosz Sypytkowski
@Horusiath
Nov 28 2015 18:46
when I said transport layer I didn't mean json - it's part of serialization mechanism not transport itself ;) @Aaronontheweb will know details, but AFAIK part of the problem is that JVM uses big endian network byte order, while .NET uses little endian
Bartosz Sypytkowski
@Horusiath
Nov 28 2015 19:00
ok guys, serious question - when we're joining two actor paths some/base/path/ and /some/child/path using /, what the result should be? Because right now it is some/base/path//some/child/path (notice double / in the middle), which is not a valid path.
Roger Johansson
@rogeralsing
Nov 28 2015 19:16
Ill check what Scala does