Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Oct 20 17:25
    valdisz synchronize #3889
  • Oct 20 17:17
    valdisz synchronize #3889
  • Oct 20 15:44
    valdisz synchronize #3889
  • Oct 20 09:22
    ismaelhamed commented #3863
  • Oct 19 23:39
    valdisz synchronize #3889
  • Oct 19 23:08
    edvinasz commented #2947
  • Oct 19 13:36
    Aaronontheweb commented #3973
  • Oct 19 13:34
    dependabot-preview[bot] synchronize #3995
  • Oct 19 13:34

    dependabot-preview[bot] on nuget

    Bump BenchmarkDotNet from 0.10.… (compare)

  • Oct 19 13:34
    dependabot-preview[bot] edited #3995
  • Oct 19 13:34
    dependabot-preview[bot] synchronize #3993
  • Oct 19 13:34

    dependabot-preview[bot] on nuget

    Bump Google.Protobuf from 3.9.1… (compare)

  • Oct 19 13:34
    dependabot-preview[bot] synchronize #3991
  • Oct 19 13:34

    dependabot-preview[bot] on nuget

    Bump Microsoft.Extensions.Depen… (compare)

  • Oct 19 13:34
    dependabot-preview[bot] synchronize #3989
  • Oct 19 13:34

    dependabot-preview[bot] on nuget

    Bump ApiApprover from 3.0.1 to … (compare)

  • Oct 19 13:34
    dependabot-preview[bot] synchronize #3992
  • Oct 19 13:34
    dependabot-preview[bot] edited #3993
  • Oct 19 13:34
    dependabot-preview[bot] synchronize #3985
  • Oct 19 13:34

    dependabot-preview[bot] on nuget

    Bump System.Reflection.Emit fro… (compare)

Natan Vivo
@nvivo
I believe if you want to communicate between 2 different systems, it's easier to build some http layer through json nowadays outside of akka and just use that
Brandon Wilhite
@JediMindtrick
and also...just because it can be done doesn't mean you should do it :)
Natan Vivo
@nvivo
yeah.. think about it, yo usually won't couple 2 applications made with different versions of .NET
even more with 2 applications made for different languages at that level
Brandon Wilhite
@JediMindtrick
don't get me wrong....I'm not advocating people should do what I'm asking about...I'm more just curious about this since the idea of rpc is kind of built into akka from the get-go
after all...if I'm sending a message to a remote actor, what should it matter what kind of runtime is running over there? But my experience with akka is limited and this is just something I've wondered about for awhile now.
i'd think supervision, deathwatch and probably other things would get pretty hairy
Natan Vivo
@nvivo
sure
from what I read here, one of the big problems would be endianess, as the protocol is binary and java and .net use different ways to encode these stuff
it would be possible if the two systems used exactly the same serializer, then you'd go into the next issues with message formats...
Brandon Wilhite
@JediMindtrick
so what kind of problems would you hit if you bumped up another level and tried to do something like akka-jvm proxy -> json over (pick your transport) <- akka.net proxy
obviously, you'd have to track liveliness somehow
Natan Vivo
@nvivo
this is the kind of question for @Aaronontheweb.
Brandon Wilhite
@JediMindtrick
k, thanks again, useful exchange
Natan Vivo
@nvivo
sure
Arjen Smits
@Danthar
@JediMindtrick if your going that route. Why use a raw HTTP endpoint with json? why not explicitly model that communication with message types. And use a messagebus like RabbitMq for that?
Joshua Benjamin
@annymsMthd
@Aaronontheweb looks like i have a few run away builds
Joshua Benjamin
@annymsMthd
@rogeralsing If you have access to the teamcity site can you cancel those runaway builds i caused?
Andrew Skotzko
@skotzko
@annymsMthd stopped them for you
Joshua Benjamin
@annymsMthd
thanks
Aaron Stannard
@Aaronontheweb
@annymsMthd our build server just really liked XUnit 1.9.2 is all
btw, just deputized you as an official contributor to Akka.NET now - you've earned it
@JediMindtrick ahhh... the joys of JVM <---> .NET wire compatibility
Joshua Benjamin
@annymsMthd
\o/
Aaron Stannard
@Aaronontheweb
pull up a chair, and hear my song: a tale of woe about endianness, built-in serializers, and wire format compatibility
Joshua Benjamin
@annymsMthd
lol
Arjen Smits
@Danthar
hehe ^^
Aaron Stannard
@Aaronontheweb
many moons ago, computer organizers decided for no apparent reason to organize words in memory in completely backwards orders
across different systems for reasons that are arbitrary
but that matters not
the JVM architects decided, for their own reasons, that big endianness was the one true way to organize bytes
and Microsoft, being the arch-nemesis of any company run by open source birkenstock-wearing hippies
decided that little endianness must be the one true way
Arjen Smits
@Danthar
birkenstock lol
Joshua Benjamin
@annymsMthd
and so the battle of endianness swept the land into darkness and despair
Aaron Stannard
@Aaronontheweb
yes, indeed
file format and wire compatibilities were hopelessly dashed
and many heated arguments between bearded UNIX-y types ensued
and for all a time, there was nothing but darkness spread across the land
Aaron Stannard
@Aaronontheweb
but as the years crept by, legends arose in the Microsoft community of new projects in JVM land
of unspeakable power
distributed databases, batch processing systems, streaming ETL pipelines
much like the citizens of East Germany living in the shadow of the Berlin wall, we dismissed these stories as just JVM propaganda
and chuckled smugly to ourselves as we patiently waited for SQL Server 2013 Super Streaming MapReduce Does Everything Edition
but as the years ticked by, these stories stepped into the realm of fact
and us CLR developers, seeing with our own eyes for the first time, decided that the great Endian war must come to an end
so we learned how to use byte[].Reverse()
But no, my sweet summer child, that was not the end
indeed... as it turns out - none of our built-in serializers are cross-platform compatible