indeed... as it turns out - none of our built-in serializers are cross-platform compatible
and thus the small light of hope we only just recently lit was in danger of being squelched by the aftermath of the Endian war after all
But we said "enough!" and developed cross-platform wire formats that used their own serializers, like Thrift and Protobufs
and finally tore the great format wall down once and for all
ok, I can't keep telling this like an Epic poem
gave it everything I had
lol
and make sure both ends serialize using that
might be as simple as adding a JSON serializer as the default for Akka
and then on the CLR side you'll need to account for endianness
probably better off just making an Akka.IO wrapper in C#
and use that to communicate as a client
rather than attempt to get Akka.Remote / Akka.Cluster to be JVM-compatible
was wondering when Galdalf the Red, Blue, Yellow and Green would come in
lol @nvivo
that's my get out of jail free card
there is no try?
there is only Do :P
I need to follow up with those guys today - think they needed @skotzko and I's powerpoints
senor @skotzko gave a talk on how to model distributed transactions with Akka.NET actors
5 minute lightning talk
he did a great job but I think Glenn Block might have cut him off lol
that'll be going live in Akka.NET v1.0.1
(the release for that was supposed to happen today but we decided it'd be best to get the Akka.Persistence.SQLServer stuff pulled in and the
ConfigureAwait stuff first)
so it'll probably end up going out Monday / Tuesday next week instead
just recommended it in this SO question: http://stackoverflow.com/questions/29819185/how-to-create-an-active-objects-pattern-typedactor-in-c-sharp?
that'd probably fall under the miscellaneous bucket
