Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 21:29
    Aaronontheweb commented #3863
  • 21:28
    Aaronontheweb synchronize #3863
  • 21:18
    Aaronontheweb synchronize #4000
  • 21:17
    Aaronontheweb commented #3964
  • 21:17
    Aaronontheweb commented #3964
  • 21:16
    Aaronontheweb synchronize #3964
  • 21:12
    Aaronontheweb commented #3964
  • 21:08
    Aaronontheweb synchronize #71
  • 21:04
    Aaronontheweb synchronize #3973
  • 21:00
    Aaronontheweb commented #71
  • 20:58

    Aaronontheweb on dev

    Akka.Persistence.TCK fix - chec… (compare)

  • 20:58
    Aaronontheweb closed #4002
  • 20:51
    Aaronontheweb synchronize #4002
  • 20:45
    Aaronontheweb commented #3811
  • 20:45
    Aaronontheweb commented #3811
  • 20:44
    Aaronontheweb labeled #4002
  • 20:43
    Aaronontheweb milestoned #4002
  • 20:43
    Aaronontheweb opened #4002
  • 20:37
    Aaronontheweb synchronize #71
  • 20:20
    Aaronontheweb synchronize #71
they don't have release in that way instead the request gets wrapped in a lifetime scope which itself is disposed.
Although if using autofac we could resolve an Owned<T> and in the release dispose that
would probably be enough
where T being the actor type
so yeah sorry release is probably enough :)
Raymen Scholten
@raymens
Is there someway to append a incrementing number to an actors name that will enforce the name to be unique? (like SomeRandomActor-Child-1, ....-Child-2, ....)
Raymen Scholten
@raymens
And is it correct that the F# API doesn't provide any F# specific stuff about creating an actor that has a constructor or any means of saving state?
Raymen Scholten
@raymens
There are probably better ways but
let actorOfCtor (state : 'a) (fn : 'a -> 'Message -> unit) (mailbox : Actor<'Message>) : Cont<'Message, 'Returned> =
let rec loop() =  
    actor {  
        let! msg = mailbox.Receive() 
        fn state msg 
        return! loop() 
    } 
loop()
allows the creation of an actor that will have some sort of initial data that is usable by the messageHandler every message
Bartosz Sypytkowski
@Horusiath
@raymens if you must use some state in F# API, pass it as a rec loop parameter , eg:
type MyState = { X: int; Y: int }
let aref = spawn system "my-actor" <| fun mailbox ->
    let rec loop state = actor {
         let! msg = mailbox.Receive()
         return! loop ({ state with Y = msg })
    }
    loop ({X = 1; Y = 2})
this way it maintain F# principles - immutable data, function as unit of composition etc.
Raymen Scholten
@raymens
thanks, that's better :)
Håkan Canberger
@HCanber
@raymens If you don't name an actor, the system will assign it a unique name. If you want the name to follow some kind of pattern, like in your example, you have to write it yourself.
Bartosz Sypytkowski
@Horusiath
@Aaronontheweb do you have some kind of the documentation or tech. overview to Helios? I'd like to see, what else purposes could it serve.
Raymen Scholten
@raymens
@HCanber allright, thank you
Raymen Scholten
@raymens
Are questions better suited for StackOverflow or gitter?
Roger Johansson
@rogeralsing
Id say gitter, most of us are here every day
Aaron Stannard
@Aaronontheweb
@Horusiath very little, although I'm in the process of migrating it to its own organization and publishing docs around Helios 2.0
the only real docs I have for at it at the moment are its specs and samples
@stefansedich submitted a PR a couple of days ago which should enable Mono support in Helios
and should fix the Akka Remoting issues
turns out that TcpClient and UdpClient call Socket.Bind in their constructors on Mono, which makes it impossible to set socket options on them
Aaron Stannard
@Aaronontheweb
@smalldave you might appreciate this, btw https://github.com/petabridge/lighthouse - took an old project I started on with Akka.Cluster a while back and I'm modernizing it now
basically it's a windows service that acts as a dedicated seed node for clusters that want to use roles
runs virtually no code other than what's in Akka.Cluster so it doesn't need to be updated
designed for PaaS environments like Elastic Beanstalk, AppHarbor, Azure Websites
I'm in the process of rewriting it to use Topshelf now
and an NLog adapter that lets it write to the windows event log
Topshelf itself is super neat - never used it until I saw some of our contributors mention it: http://topshelf-project.com/
David Smith
@smalldave
+1 for Topshelf. Been using it for years. Microsoft should have adopted by now
lighthouse looks interesting
Aaron Stannard
@Aaronontheweb
yeah, this is way better than the alternatives
can't believe I hadn't used it until now
the idea behind lighthouse is basically to have a 1-2 lighthouse instances sitting on dedicated IaaS boxes
it's meant to be a scriptable, configurable Akka.Cluster service that you will eventually just be able to deploy via a packaged binary
and some .config modifications
the idea is to just keep a couple of these around as a lightweight, do-it-yourself Akka.Cluster service discovery endpoint
they're not necessary in environments where you can use something like the EC2 SDK to query all of the IPs of other machines in your deployment group
David Smith
@smalldave
think it's a good idea and good name!
Aaron Stannard
@Aaronontheweb
awesome, glad you like it :)
the code's super simple - mostly just some configuration injection stuff
David Smith
@smalldave
was @Horusiath talking about being able to deploy actors along with their code remotely in F#? makes a no frills cluster node interesting
Aaron Stannard
@Aaronontheweb
yes he was
I think there's a way that can be done generically too
David Smith
@smalldave
not sure how I feel about that. bit scary :)
Aaron Stannard
@Aaronontheweb
I was drafting a proof of concept idea for a talk @skotzko and I are giving later this month on doing Streaming ETL with Akka.NET
had the notion of allowing end users to install a NuGet package and write a .NET assembly that implements a few interfaces for doing Extract / Transform
and distributing that across the cluster - having specific actors deployed who use that code internerally since it knows how to construct objects with that interface