These are chat archives for akkadotnet/akka.net
ReceiveActorand defining some base Receivers in it's constructor, and concrete actor
Athat is created using castle windsor DI. But when DI creates instance of
B, I receive null exception - it turns our that list of receivers of actor
Bis empty (as it didn't introduced any for itself, inheriting only those from
A) - it looks like receivers defined by
Ahave been cleared out.
protected override bool AroundReceive(Receive receive, object message)receive parameter passed is null
using LeNameSpace = System.Original.Namespace.Messages
using abc = Shared.Messages;and my sender used
using cba = Shared.Messages;would the Receive<abc.message> still be hit if the sender sent cba.message?
Additional information: 'akka.actor.provider' is not a valid type name : 'Akka.Remote.RemoteActorRefProvider, Akka.Remote'from the
ConfigurationFactoryI went and tried your chat server sample with it and got the same, any ideas?
paket.targetsfrom all project files
Throttlerpattern into Akka.Pattern
demand- it's basically a number which tells how many message subscriber can buffer
Request(int)with it's current demand. Current demand is (max demand - bufferedMessages.Count)
Requestmessage from subscriber, publisher remembers current demand and when it receives new message it publishes it and decreases demand number - since publishers/subscriber relation is 1-1, it's easy to keep track of current demand
contributing.mdlays out a fool-proof Git workflow for doing this. Read it first before you contribute! https://github.com/akkadotnet/akka.net/blob/dev/CONTRIBUTING.md
devbranch and into feature branches
git cherry-pickand the commit numbers you provided
git checkout -b 1410-fix
git branch -D dev
git push origin :dev