Thanks!
> On Oct 26, 2016, at 2:35 AM, Patrik Nordwall
> wrote:
>
> ask is fine as long as you don't close over something that is not thread-safe
> in callbacks of the Future. It should be low risk of mistake in mapAsync
> since you typically only return the Future (after casting/mapTo to the
ask is fine as long as you don't close over something that is not
thread-safe in callbacks of the Future. It should be low risk of mistake in
mapAsync since you typically only return the Future (after casting/mapTo to
the right type).
I updated the Streams documentation for integration with actors
I should add that the ask() I would be inserting would actually be to the
ShardRegion for a shared, persistent actor.
On Tue, Oct 25, 2016 at 11:33 AM, Richard Rodseth
wrote:
> Anyone else? Suppose I need a stage that just looks up something that is
> contained in a (persistent) actor.
> Is it g
Anyone else? Suppose I need a stage that just looks up something that is
contained in a (persistent) actor.
Is it good practice to use mapAsync with an ask() to that actor?
Or is there some other stage that would let me use the actor to transform
one stream element to another without sacrificing ba
