These are chat archives for akkadotnet/AkkaStreams

24th
Jan 2017
Arjen Smits
@Danthar
Jan 24 2017 10:08
Im looking for a way to utilize a broadcast stage, where the flows its broadcasting to are dynamic. In my use case each flow the broadcast stage should publish to does its own filtering, and the number of stages are dynamic and can change at runtime.
so at one point it may be broadcasting to 2 other flows, and then 1 minute later there may be 4
is there anything in akka.streams that allows me to do this ? Or do i need to get creative
Arjen Smits
@Danthar
Jan 24 2017 10:15
i guess what im looking for is a way to connect or disconnect flows from an broadcast stage at runtime
Marc Piechura
@marcpiechura
Jan 24 2017 10:25
@Danthar BroadcastHub is probably what you are looking for. http://doc.akka.io/docs/akka/2.4/scala/stream/stream-dynamic.html
I have ported it and it should be included in 1.3
thx @Silv3rcircl3 ill go look into that
Arjen Smits
@Danthar
Jan 24 2017 10:38
thx @Silv3rcircl3 that was exactly what i was looking for :P
one think though
the docs dont mention anything about removing items from the broadcasthub
eh, subscribers
ah nvm, need to read the entire thing before commenting
Marc Piechura
@marcpiechura
Jan 24 2017 11:20
:)
Arjen Smits
@Danthar
Jan 24 2017 11:21
my next challenge is to create an retry stage. That monitors a downstream stage and retries the same stage if an exception is thrown
but i think i might have to do that by creating a custom stage that handles both concerns in one definition. So it does behavior A but also catches exceptions and retries when it fails.
Or is there a new stage that allows me to perform atleastonce delivery on a stage ?
Marc Piechura
@marcpiechura
Jan 24 2017 11:23
There is a retry stage but I'm not sure how the behavior is
Arjen Smits
@Danthar
Jan 24 2017 11:23
yeah the continuewithretries
but that thing forces you to define an alternative stage
Marc Piechura
@marcpiechura
Jan 24 2017 11:23
Ah yeah right
Arjen Smits
@Danthar
Jan 24 2017 11:23
where the message goes if its retried
Marc Piechura
@marcpiechura
Jan 24 2017 11:24
Then you need a custom one
Arjen Smits
@Danthar
Jan 24 2017 11:24
maybe i dont understand that thing correctly. but it seems useless to mee
i want to retry the message, and if it fails after x retries, then log it.
or in my case, retry indefinetly. Since in my scenario im interested in the ability to handle intermittend network failure
since the source gets its work from the network as well. If there is no network, no new work comes in, so im not to afraid about buffer overruns or something
Marc Piechura
@marcpiechura
Jan 24 2017 11:43
I could take a look in the next days, don't have time at the moment ;-)
Arjen Smits
@Danthar
Jan 24 2017 12:38
np