These are chat archives for akkadotnet/akka.net

21st
Dec 2017
HermansG
@HermansG
Dec 21 2017 12:34
@diegolinan We apply the specific configuration files in the build, easy and clarifying.
When an actor is told to stop, can we be sure that all memory is released for gc? Do we need to still dispose anything?
Diego Liñan
@diegolinan
Dec 21 2017 12:36
@HermansG That's another one... But I'd rather use the transforms for clarity on what's happening...
Aaron Stannard
@Aaronontheweb
Dec 21 2017 16:10

btw why do we target several platforms rather than just a standard ?

yeah, what @boekabart said

we didn't want to break backwards compat with people who were using us on .NET 4.5 just yet
and some features that users depend on, such as automatic config loading, don't have an equivalent solution on .NET Core just yet
since ConfigurationManager is no longer supported
we're going to do a Microsoft.Extensions.Configuration implementation in Akka.NET v1.4
which will help standardize us on the new, .NET Standard-centric APIs
Maxim Cherednik
@maxcherednik
Dec 21 2017 16:12
yeah, I thought so, I am not yet into it... with several platforms at the same time... Just trying to figure out how it works then
Aaron Stannard
@Aaronontheweb
Dec 21 2017 16:12
think of it as a crutch until the .NET ecosystem has some time to catch up
we also had some problems with certain libraries not supporting .NET Standard at all, mostly some of the F# ones
.NET Standard 2.0 resolves all of that
and we might upgrade to .NET Standard 2.0 in a later release
we choose not to do it with Akka.NET 1.3 because it literally came out the same week we were doing the release
and give the .NET Core team's rather poor track record with v1 build quality
we didn't want to gamble on that stuff working just right out of the box
Jack Wild
@jackowild
Dec 21 2017 16:17
eta on 1.4?
Aaron Stannard
@Aaronontheweb
Dec 21 2017 16:17
sometime next year
the earlier the better
the config changes might be really expensive to implement from a developer time perspective not because they're complicated
but because there's just a lot of them and a lot of tests that cover them
Juan Suero
@juansuerogit
Dec 21 2017 17:44
If i have .Net core clients on linux using actors, can those actors address actors in other runtimes as well? For example if if i have .NET 4.6.1 clients using actors, and also actors in .net core on windows?
like if i had a common actor "backplane" in one runtime that can talk to these child runtimes? does this makes sense?
Aaron Stannard
@Aaronontheweb
Dec 21 2017 17:55
@fogbridgegit yes they can but you'd want to define a schema-based serializer for that
i.e. Protobuf
our built-in polymorphic serializer has trouble going between .NET Core and .NET Desktop
due to the fact that namespaces for built-in types like string are different between .NET Core and .NET Desktop
Juan Suero
@juansuerogit
Dec 21 2017 17:56
wow sounds hard im more like an psuedo entreprenuer technologist cobble together things.
what about .NET core to .NET core same runtime but different processes?
Aaron Stannard
@Aaronontheweb
Dec 21 2017 17:57
you can thank Microsoft for making that hard :p
yep, that can work seamlessly
Juan Suero
@juansuerogit
Dec 21 2017 17:57
pheew ok :)
Juan Suero
@juansuerogit
Dec 21 2017 18:04
What about .NET core akka actors talking to your original Akka system .. on Java? Scala? or something i forget. if so , Is there a sample project?
im guessing it would have to be the same answer. " define a schema-based serializer" ... so if i can put that in laymens terms... You are saying i can ADDRESS other actor systems in different runtimes just fine and everything Akka based, all its underlying protocols will work. except at the data type level I need to explicitly define the SHAPE of the data. akka wont do that bit for me.
Bartosz Sypytkowski
@Horusiath
Dec 21 2017 19:04

@fogbridgegit I know it is possible, but:

  1. Requires some configuration (i.e. .NET/Java are using different byte ordering, but this can be changed via config).
  2. You need to serialize your messages using custom serializer, which will be understood by both .NET and JVM i.e. protobuf.

Also I've heard that @Aaronontheweb got some progress on a field of akka-cluster across .NET and JVM, maybe he can tell more

Juan Suero
@juansuerogit
Dec 21 2017 19:25
ok thanks bro. i dont need it yet but somewhere down the line definitly
David Rivera
@mithril52
Dec 21 2017 20:11
@Horusiath I am starting to try to use DistributedData for a project I'm working on. So far, I'm not having a lot of luck. I keep getting error messages about Akka not able to find a sterilizer id. Is this a known issue?
*serializer
Bartosz Sypytkowski
@Horusiath
Dec 21 2017 20:50
@mithril52 have you added DistributedData.DefaultConfig() for fallback?
David Rivera
@mithril52
Dec 21 2017 22:22
@Horusiath Hmm, no. I will have to try that, thank you.