Re: [akka-user] Akka-Typed MutableBehavior: return type of onMessage

I am not able to understand when to make use of it instead of always returning 'this' outside the match block in MutableBehaviour. Sounds redundant right now, but maybe I need to write a bit more code to see the utility. On Wednesday, July 19, 2017 at 5:20:19 AM UTC+5:30, Konrad Malawski

Re: [akka-user] Akka-Typed MutableBehavior: return type of onMessage

Exactly the same. Becoming an different behavior. On July 19, 2017 at 0:16:18, Mushtaq Ahmed (mushta...@gmail.com) wrote: > Actor.immutable returning Behaviour[T] makes sense as it uses recursion to > return updated state or Actor.stopped etc. > > But in MutableBehavior, I end up using this

[akka-user] Akka-Typed MutableBehavior: return type of onMessage

Actor.immutable returning Behaviour[T] makes sense as it uses recursion to return updated state or Actor.stopped etc. But in MutableBehavior, I end up using this pattern a lot. override def onMessage(msg: Msg): Behavior[Msg] = { msg match { case M1 => //unit returning action

Re: [akka-user] Cannot stop actor running akka stream

Hi, There is nowhere in that shared snippet where you actually use the kill switch to stop the stream? A reasonable place to use the kill switch would be the postStop hook of the actor. This 3 part series of articles by Colin Breck may help:

Re: [akka-user] Akka Typed API discussion

It looks like if you were writing anything that wrapped another Behavior you would have code that is like what is in Widened which has to allow for Same, Deferred and Unhandled. If you look at Immutable as a potential model for wrtiting a simple class that extends behavior you see it is

Re: [akka-user] Akka Typed API discussion

There already is ExtensibleBehavior, does that not provide you with all the access and tools you need? > 18 juli 2017 kl. 13:53 skrev Bryan Murphy : > > I mostly agree with you and the NamedStateBehavior may only be useful when > you have well defined state transitions

Re: [akka-user] Akka Typed API discussion

I mostly agree with you and the NamedStateBehavior may only be useful when you have well defined state transitions (low change frequency) or not useful at all but the point is it I could write it and decide if it was useful if Behavour supported being extensible. I can't see how I could do

Re: [akka-user] Akka Typed API discussion

Hi Bryan, thanks for articulating your points! Regarding the first one I’d like to widen the scope of the discussion: is it useful to access the private state of a state machine for testing purposes? I know that I am guilty of creating the akka-testkit nearly seven years ago, allowing

Re: [akka-user] Akka Typed API discussion

Hi Bryan, The forum differs a bit depending on what you want to chat about. Do you have a few issues to talk about and they’re specific enough (and potentially could have an actionable outcome I’d assume/hope)? Then http://github.com/akka/akka would be the best, one ticket per specific issue, not

[akka-user] Akka Typed API discussion

Where is the best place to discuss the Akka Typed API ? I am hoping it is still open to change as I have some (reasonably lengthy) comments and suggestions to make so I want to make sure I give them in the correct forum. Is it here, a gitter channel, a github issue or somewhere else ? Thanks