Re: [akka-user] Overriding onUpstreamFinish behaviour for FlowOps

As a follow-up, I’ve implemented a custom half close stage after having a good night’s sleep and thinking about it. :-) First, the simple half-close custom stage: https://github.com/huntc/landlord/pull/14/files#diff-b745088184322d5d8e53de44d17b9ca6R262

Re: [akka-user] Overriding onUpstreamFinish behaviour for FlowOps

Thinking about it, what I’m trying to do is implement halfClose behaviour as per Tcp. > On 27 Nov 2017, at 16:17, Konrad “ktoso” Malawski > wrote: > > What kind of Flow exactly. What does it do? > See this too > https://doc.akka.io/docs/akka/current/stream/stream-error.html?language=scala#del

Re: [akka-user] Overriding onUpstreamFinish behaviour for FlowOps

> On 27 Nov 2017, at 4:17 pm, Konrad “ktoso” Malawski > wrote: > > What kind of Flow exactly. What does it do? I’m implementing Unix Domain Sockets and the following interface borrowed from Tcp: def outgoingConnection( remoteAddress: UnixSocketAddress, localAddress: Option[UnixSocketAddre

Re: [akka-user] Overriding onUpstreamFinish behaviour for FlowOps

What kind of Flow exactly. What does it do? See this too https://doc.akka.io/docs/akka/current/stream/stream-error.html?language=scala#delayed-restarts-with-a-backoff-stage other than supervision which isn’t generic. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Li

[akka-user] Overriding onUpstreamFinish behaviour for FlowOps

Hi there. I've got a requirement for a flow to keep going when its upstream input completes/fails. I could write a custom flow stage and override onUpstreamFinish, but I was wondering if there were a means to express this just using the FlowOps API. FlowOps.detach got me excited, but that isn't