Hi Jakob,
Let us know how that solution fares!
--
Cheers,
√
On Jan 29, 2016 8:10 PM, "Jakob Odersky" wrote:
> Hey Viktor,
> I never thought of using the underlying reactive streams API directly
> but it sounds like a good idea!
>
> cheers,
> --Jakob
>
> On Fri, Jan 29, 2016 at 12:45 AM, Viktor
Hey Viktor,
I never thought of using the underlying reactive streams API directly
but it sounds like a good idea!
cheers,
--Jakob
On Fri, Jan 29, 2016 at 12:45 AM, Viktor Klang wrote:
> Hi Jakob,
>
> Perhaps create a fanout Publisher from the Sink and materialize the
> consumers as Subscribers a
Hi Jakob,
Perhaps create a fanout Publisher from the Sink and materialize the
consumers as Subscribers and connect them to the Publisher?
--
Cheers,
√
On Jan 28, 2016 6:28 AM, "Jakob Odersky" wrote:
> What is the best approach to "connecting" streams at run-time?
>
> My use-case is a server th
What is the best approach to "connecting" streams at run-time?
My use-case is a server that has an established connection to some
backend service, modeled as a flow. Several clients can connect
through websockets, also modeled as flows.
If the number of clients was known at materialization, this
