Re: [akka-user] Flow.mapAsync and downstream demand

2018-02-23 Thread Jeff
Actually found a much simpler solution using Source.unfoldAsync. On Thursday, February 22, 2018 at 6:54:54 PM UTC-8, Jeff wrote: > > My particular use case is a long poll where the id to be sent on the next > request is returned from the previous request. > > On Thursday, February 22, 2018 at

Re: [akka-user] Flow.mapAsync and downstream demand

2018-02-22 Thread Jeff
My particular use case is a long poll where the id to be sent on the next request is returned from the previous request. On Thursday, February 22, 2018 at 6:40:48 PM UTC-8, Konrad Malawski wrote: > > In general relying on exact timing of pulls is rather seen as an anti > pattern… > Even if you

Re: [akka-user] Flow.mapAsync and downstream demand

2018-02-22 Thread Konrad “ktoso” Malawski
In general relying on exact timing of pulls is rather seen as an anti pattern… Even if you do a custom stage, it’s very brittle, as any element put before your stage could cause pulls, simply because that’s how things work. The same can be said about simply changed buffer sizes between stages —