Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 09:00
    Horusiath commented #4077
  • 06:31
    Aaronontheweb commented #4085
  • 06:28
    Aaronontheweb commented #4085
  • 06:24
    Aaronontheweb commented #4085
  • Dec 07 11:49
    IgorFedchenko commented #4085
  • Dec 07 10:31
    IgorFedchenko commented #4085
  • Dec 07 08:36
    IgorFedchenko commented #4085
  • Dec 06 20:57
    IgorFedchenko commented #4085
  • Dec 06 20:32
    IgorFedchenko commented #4085
  • Dec 06 20:01
    IgorFedchenko commented #4085
  • Dec 06 19:55
    IgorFedchenko commented #4085
  • Dec 06 16:22
    Aaronontheweb labeled #3997
  • Dec 06 16:22
    Aaronontheweb closed #3997
  • Dec 06 16:20
    IgorFedchenko commented #3997
  • Dec 06 16:08
    IgorFedchenko commented #4085
  • Dec 06 15:50
    Aaronontheweb assigned #4085
  • Dec 06 15:50
    Aaronontheweb labeled #4085
  • Dec 06 15:50
    Aaronontheweb labeled #4085
  • Dec 06 15:49
    Aaronontheweb closed #4032
  • Dec 06 14:58
    IgorFedchenko commented #4032
Michael Chandler
@optiks
@Aaronontheweb any idea if the CreateTestProbe() behaviour change was deliberate? (see more detail above)
fanoI
@fanoI

Is it possible to launch the UI Event Loop from an Actor? Only if that Actor will exist the GUI should run this works with a Command Line application but not in Akka.Net Actor:

       [STAThread] //optional
        protected static bool StartUILoop()
        {
            Application.Run();
            return true;
        }

        protected override void PreStart()
        {
            /* Let's start an Empty UI Application, the true Application will load the page with "Loading..." */
            //Task mytask = Task.Run(() => Application.Run());

            Task mytask = Task.Run(() =>
                StartUILoop()
            );
        }

then when I receive the load command I simply do:

                    var form = new LoginForm();
                    form.Show();

the form is effectively shown but is not working is not active, label text is not drawn and if I move the mouse in it I get the spin wheel!

Thank you for your help...

I've tried to create the Actor in the UI thread using dispatcher = akka.actor.synchronized-dispatcher but nothing changes I suspect it is because I've created a Task not the normal UI thread
Marc Piechura
@marcpiechura
@Tochemey we have ported the complete documentation from the jvm too. Can you give me a link with the tutorials your referring to?
Arsene
@Tochemey

@Silv3rcircl3 I have gone through few of them.
https://www.slideshare.net/Lightbend/understanding-akka-streams-back-pressure-and-asynchronous-architectures?next_slideshow=1

https://www.slideshare.net/rolandkuhn/akka-streams-and-http

https://github.com/pkinsky/akka-streams-example

https://www.slideshare.net/joy87/a-dive-into-akka-streams-from-the-basics-to-a-realworld-scenario

The documentation is great. I am disputing that. However you gusy have used in production if you guys can write some tutos like the one Bartosz wrote on Akka.IO it will help us as starting point.

Marc Piechura
@marcpiechura
The example from pkinsky is probably worth porting it. I think the only one that is using Akka.Streams in production is @Aaronontheweb ;-) And we have the webcrawler example that is now using Akka.Streams, see petabridge/akkadotnet-code-samples@fcc6025
Aaron Stannard
@Aaronontheweb
@optiks the change was deliberate
ensures that the test probes and test actors only get shut down after the user-defined actors
did that end up breaking some of your specs?
(it also was meant to bring us in line with the JVM)
Michael Chandler
@optiks
@Aaronontheweb Okie, thanks. Yep, it broke some of tests which were testing code which was using ActorSelection
mhsjlw
@mhsjlw
Hey! I'd like to implement a game server in Akka.NET using F#, can anyone point me to docs for using TCP I/O in F#? I can't find any other than the C# ones
Weston
@ronnyek
I'd really like to utilize akka.net, I wish the timing was better. Sadly it seem slike there are options that support netcore or will in the very very near future =(
seems like there is a possibility of that in AKKA.net world
but that soem of these issues have just een oustanding for a while
Bartosz Sypytkowski
@Horusiath
@mhsjlw here is the basic TCP listener in Akkling: https://github.com/Horusiath/Akkling/blob/master/examples/io.fsx
but it's using pure actors, not streams. I'll try to provide some examples of stream-based TCP once I'll have finish #2405 (which is actually already complete, but I want to focus on better memory usage and potential micro optimizations)
Arsene
@Tochemey
Hello does Akka Stream has scodec?
as one the in-built Stage
Arsene
@Tochemey
Hello how can I use the Akka Streams with F#?
Arsene
@Tochemey
Hello
Does Akka provides some common functional type like Option,Some, None and so forth...
Alex Valuyskiy
@alexvaluyskiy
@Tochemey Option, Some, etc came from Scala, not Akka. There is not equivalents in C#. But you can use Option in F#
Arsene
@Tochemey
@alexvaluyskiy I thought they have implemented utility classes to cater for that since it a port.
Bartosz Sypytkowski
@Horusiath
@Tochemey Akkling.Streams offers F# API over akka.streams
including support for Option and unit
Damian Reeves
@DamianReeves
Anyone have any experience using Akka with Hangfire?
Aaron Stannard
@Aaronontheweb
@DamianReeves that's error tracking and monitoring right?
Damian Reeves
@DamianReeves
Job sheduling... more modern Quartz
Aaron Stannard
@Aaronontheweb
whoosh
my bad
Damian Reeves
@DamianReeves
Our web guys want to use that over quartz so now I need to look at integrating it with akka instead of using Quartz
Bartosz Sypytkowski
@Horusiath
@DamianReeves Quartz interop is like 1-2 actors
Damian Reeves
@DamianReeves
Yeah... I'm all for quartz causes its simple
but looks like I lost out as they don't want to maintain 2 sets of scheduling tables
and hangfire has a nice UI
Bartosz Sypytkowski
@Horusiath
I mean interop with hangfire shouldn't take much more
Damian Reeves
@DamianReeves
I see what you mean
Alright I'll head down that whole... hopefully I'll come out with something for the community
:smile:
Chris Ochs
@gamemachine
So a common pattern in multiplayer games is actually the orleans approach, due to everything being very stateful. Like you are running a lot of game instances where each one has to be accessible from nodes players are actually connected to. I put together a system for managing this, where you create an actor, it's hashed to a node and any node can easily get a reference to it. Currently it uses redis for persisting the state. Also handles the case of remote not yet started by having a manager on each node that creates the actors, and if a local node doesn't yet have an actor ref, it routes the request through the manager. If there is enough interest in this I was going to make it into a contrib module or something.
Chris Ochs
@gamemachine
It's also useful where you need multiple singletons. Like when a player asks for an open game to join, and you don't want to partition that space you want to handle it as efficiently as possible, you have no choice but to route that decision through a single point, synchronize on global state. matchmaking posed the same issue, as did a number of other features that are fairly common to games
advapiIT
@advapiIT
Hello, I need to know if akka can fit my needs, I have to perform tcp socket communication to a c++ server that sends financial data, till now I've used supersocket but I'm facing some problem I think they're related to supersocket itself . I was wondering how trivial (and if it's possible) to set up akka to use to implement reactive pattern to tcp sockets
Ricky Blankenaufulland
@ZoolWay
there was a post somewhere how to use actors as great async TCP sockets... cannot find it at the moment
advapiIT
@advapiIT
can it be this one?
Ricky Blankenaufulland
@ZoolWay
no, thats about java akka
Ricky Blankenaufulland
@ZoolWay
When migrating to Akka.NET Remote 1.2, will I have to change in akka.hocon the TCP configuration from akka.remote.helios.tcp to akka.remote.dotnetty.tcp? The blogpost ( https://petabridge.com/blog/akkadotnet-12-cluster-streams/ ) mentions that section for TLS configuration but nothing about migrating existing applications.
Nick Chamberlain
@heynickc
@ZoolWay afaik there is backwards compatibility https://github.com/akkadotnet/akka.net/blob/master/src/core/Akka.Remote.Tests/Transport/BackwardCompatibilitySpec.cs. however, if you want to use TLS, you have to use dotnetty transport
Chris Ochs
@gamemachine
Re tcp sockets in akka, my suggestion is just don't. It needlessly complicates an already complex thing. I tried out the java version of tcp/udp handling a few years back, it resulted in just convoluting the code for no good reason, and it performed terribly (just their bad implementation most likely, lots of extra copying because of the naive let's apply immutability where it's not needed)