I would look into that tomorrow
get your code to work and then you can worry about the setup :p
I'm still dealing with issues related to my Windows 10 and VS 2015 upgrade
the build step builds
Akka.sln how do I tell it to skip fsproj projects?
I think this is a change you'd be making at the solution level
Solution --> Properties --> Configuration
and you can turn off the individual FSharp projects
should be about 6 of them
but for the time being, you can temporarily leave it that way while you work on your stuff - rather than have to fight with VS and the F# installer :p
but the test I ported is failing so i would not submit the PR just yet
or if you like, I can submit the PR only for the change to fake file
send in one PR for the FAKE change
and IMHO, may as well put in another PR for the test - even though it's failing
that way I can look at it
looks like all of those updated Akka.Remote and Cluster docs are starting to pay off: http://stackoverflow.com/questions/32094660/how-to-detect-remote-actor-disconnection-dissociation#comment52104082_32094660
able to use the new docs to answer their own question
@bruinbrown (or anyone else who can answer): Related to a question about spray and the ability to hook up a REST interface to an actor system (e.g. so we could provide a way to query some property stored within some actor), you said the following:
Akka-Http is an existing Akka project by the developers of Spray and Tyrpesafe designed to make a HTTP API interface which works directly with actors themselves http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0-M2/scala/http/. If you're not wanting to wait for the release of Aka.Http then it's possible to use any of the existing HTTP API libraries (ASP.Net WebAPI, Nancy, WCF etc) and there's a couple of options on getting your API endpoints connected to your actor system
Can someone elaborate on the currently available "options of getting your API endpoints connected to your actor system"? I'm loving the possibilities with akka.net, just not sure how to "get data out of" it. For example, let's say I'm building an actor system that does something like keep a multiplayer game's player attributes up to date. Then I'm building a web site where I can show current stats on a set of users. I'm thinking the website needs to somehow "look into" the actor system to grab some set of stats from one or more actors. (So it's basically making queries against the actor system from outside the actor system itself.) Are there any examples/patterns to do something like this?
@softwaremike I use an actor in the API implementation to communicate with the actor system.
In your case there is either the option to push messages with the player attributes to the actor in the API or the API actor asks the actor system for the data.
The latter would use async communication (Tell), or have an Ask with async/await in a thread.
Communication to the client can be done via web sockets (SignalR or similar) to push data to the web client and update when data is available. The Web Crawler example is using this approach: Samples.
In your case there is either the option to push messages with the player attributes to the actor in the API or the API actor asks the actor system for the data.
The latter would use async communication (Tell), or have an Ask with async/await in a thread.
Communication to the client can be done via web sockets (SignalR or similar) to push data to the web client and update when data is available. The Web Crawler example is using this approach: Samples.
@Horusiath et all, are there any java/c# samples out there for you work with persistent actors? i have read through the http://getakka.net/docs/Persistence docs, but i am still pretty consufed about how to work with this api... for example, do i need to handle Receive, ReceiveCommand, ReceiveRecovery, etc...
i would like to start with something simple that can persist a few events and rebuild its state on failure
you can look at my example, I'll finish it some day probably :P
I want to change some of the patterns presented, but some basic concepts are already there
and handle ReceiveCommand instead
i am looking at the example too
once i get to a good stopping point i would like to help with docs for this, i think using code snippets from the sample might serve us better the the current persistent docs
@softwaremike you can hook up Akka.Net to any of the existing Web frameworks, essentially all you need to do is look up an actor in your actor system typically by doing something like system.ActorSelection("/user/MyActorA/MyActorB") and then once you've got that reference you can easily send data into the system by just using Tell on that address to pass it a message, if you want to then get data out, you can use Ask, which async sends a message and awaits a response from the target (it's up to the target to remember to send back a response, there's no RPC in Akka.Net). Alternatively you can use SignalR and push data down to the clients (this fits in more with the reactive nature of Akka.Net).
@softwaremike Here's a simple example of how using ASP.Net Web API 2, you can get data out of the actor system https://gist.github.com/bruinbrown/14a8fc8cfa30ef667135
boom!
