Thank you very much! I discover new things every day.
Le mardi 20 septembre 2016 17:56:24 UTC+2, drewhk a écrit :
>
> Isn't that just simply:
>
> requests.via(outgoingHttpConnection).flatMapConcat { resp =>
>resp.dataBytes
> }
>
> ?
>
> On Tue, Sep 20, 2016 at 4:42 PM, Victor > wrote:
>
>> So
Isn't that just simply:
requests.via(outgoingHttpConnection).flatMapConcat { resp =>
resp.dataBytes
}
?
On Tue, Sep 20, 2016 at 4:42 PM, Victor wrote:
> Sorry for the spam. To make it simple, what I really want to achieve is to
> have a continuous flow of ByteString from an unique HTTP conn
Sorry for the spam. To make it simple, what I really want to achieve is to
have a continuous flow of ByteString from an unique HTTP connection.
HttpRequest in, ByteString out, not multiple HttpResponse with each their
sub-source.
Le mardi 20 septembre 2016 16:30:24 UTC+2, Victor a écrit :
>
> T
Thanks for your response. I don't see where alsoTo can help me here? I
think what I want to achieve here is to join a graph with the graph
obtained by materializing the MergeHub.
Le mardi 20 septembre 2016 15:02:39 UTC+2, √ a écrit :
>
> Hi,
>
> Flow[T].alsoTo(sink)?
>
> --
> Cheers,
> √
>
> On
Hi,
Flow[T].alsoTo(sink)?
--
Cheers,
√
On Sep 20, 2016 2:30 PM, "Victor" wrote:
> Hi,
>
> Is it possible to create a Source from a Sink ?
>
> I want every element received in the Sink to be emitted from the Source.
>
> I have to do that because I use a MergeHub and a feedback loop.
>
> Thank
