@Silv3rcircl3 It's nots that simple! I think I've fiund a solution, when I validate it, I'll let you know--you never know, I might release it as open source!
+
All Conversations
Activate or click this element to toggle the profile menu
Search
Favourites
People
akkadotnet
•
Home
•
Billing
•
Get Gitter Apps
•
Allow Private Repo Access
•
Sign Out
Add a room
akka.net
Leave
Hide
Your Suggestions
SuaveIO/suave
aurelia/Discuss
akka/akka
mono/mono
dotnet/corefx
dotnet/coreclr
akka-bootcamp
helios-io/helios
IdentityServer3
visualfsharp
TypeScript
Rx.NET
Your Organisations
Twitterizer
It's not that somple. I think I've got a solution though, when I find one, I'll let you know!
@seanfarrow let me know if you need some help. Also maybe my Azure adapter can give you some inspiration, don't know how Redis works but maybe it helps https://github.com/Silv3rcircl3/Akka.Streams.Azure
vacation and doing remote work :p
In the UK at the moment; should be here through the end of the next week
but will go through all of this once I'm back
probably going to do a small point release soon with some minor Streams bug fixes, fixes for the priority mailbox, and others
also thinking about sending in a PR to skip some of the specs we know to be broken like the ClusterClient specs
no point in just re-running stuff repeatedly when the thing under test doesn't work
there's some specs, like the ActorsLeakSpec in Akka.Remote, that are just super complicated and can time out when things get busy... which makes me think maybe I should $$$ and increase the size of our VMs
basically just iterate over all members and select them by their role
I am checking out a WebCrawler sample updated by @Aaronontheweb, the akka-streams branch revised to use Akka.Streams. Am I correct that the sample is not finished and quite a lot code may be removed? Right now it looks like Stream implementation is added on the top of the old code, so it's a hybrid sample supporting both plain actors and Akka streams. Is this so?
Problem is that the reactive stream protocol works with demand that is send upstream and needs full deliver guarantees because otherwise the stream would deadlock
Cc @Aaronontheweb
Perhaps @Aaronontheweb can clarify it that example needs some cleanup.
Oh you already answered my next question, but can I combine actors and non-actors in the same flow?
What exactly do you mean by "actors and non-actors in the same flow" ?
Great :) all the select / where / GraphDSl methods only create a blueprint of the stream, they doesn't start any actors nor is any work started until you call one of the Run methods. When you do so the materializer creates actors as needed based on your settings and graph. For example you could disable fusing and therefore every stage would run in its own actor
using Streams heavily in a real project right now and that's informed my tastes somewhat
so I'll be refining it before I publish it, as well as deleting much of the old code
@mmisztal1980 I need to update it to 1.1.2 Akka
that should fix it
DNS / IPv6 stuff
hey guys, from http://getakka.net/docs/clustering/cluster-overview I read: "NOTE: Akka.Cluster is currently a pre-release nuget package, so you'll need to set the pre flag when you install it into your applications. Akka.Cluster will be considered "fully released" once Akka.NET v1.1 ships." -- I thought both Akka .NET 1.1 and Akka.Cluster were already out, so is this just a case of outdated documentation? :)
You are more then welcome to do a PR :)
Make a commit to your fork, and do a PR from there
I'll give it a try later, thanks :)