Hey yeah the PR will greatly help.
Also any chance about the second question? How to generalize my
Broadcaster? So that I have one Publisher and get a multiple publishers
out? (specifiable by the number)
Am Samstag, 22. August 2015 18:42:55 UTC+2 schrieb Konrad Malawski:
Somehow Google
Hello, currently I have an actor which gets a Publisher,
this publisher has either one or multiple elements.
Based on that I want to run through this data and send the values to
multiple Subscribers (fan-out)
One should process it and get additional data from a database (which
returns a future)
Hey I looked at it however I thought that Broadcast also needs a merge
afterwards, but I don’t need the merge?!
Also I didn’t understand the Stream Graphs, currently. Would be great to have a
example without any merge
Am 22.08.2015 um 12:56 schrieb Konrad Malawski
What you're looking for is a Broadcast operation.
Here's docs about how to use it:
http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0/scala/stream-graphs.html
--
Cheers,
Konrad Malawski
Akka @ Typesafe
On 22 August 2015 at 12:16:58, Christian Schmitt (c.schm...@briefdomain.de)
Thanks somehow I always visited the wrong documentation...
Am Samstag, 22. August 2015 12:56:27 UTC+2 schrieb Konrad Malawski:
What you're looking for is a Broadcast operation.
Here's docs about how to use it:
What do you mean by the wrong documentation?
We'd like to improve the docs (maybe add links etc), so it would help if you
could explain what was confusing for you here.
You don't need a Merge, just don't put one in your graph.
You can use this example as basis for your code:
Somehow Google points to the M2 release which only has FlowGraph {implicit b
=} which of course doesn’t work.
The 1.0 documentation is really good (if you find it..)
Especially:
http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0/scala/stream-composition.html
Somehow Google points to the M2 release which only has FlowGraph {implicit b
=} which of course doesn’t work.
The 1.0 documentation is really good (if you find it..)
Ah I see, yes that's something we should work on with our SEO optimisation I
think...
I also thought of putting up a warning
