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

typed actors this is supported with context.become > > /Patrik > ons 19 juli 2017 kl. 06:11 skrev Mushtaq Ahmed <mushta...@gmail.com>: > >> I am not able to understand when to make use of it instead of always >> returning 'this' outside the match block in MutableBehaviour. So

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 (mush...@gmail.com > ) wrote: > >> Actor.immutable returning Behaviour[T] makes sense as it uses recursion >> to return updated state or Actor.stopped etc.

[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] Akka-Typed on a new project?

On Thu, Jul 13, 2017 at 8:35 PM, Patrik Nordwall wrote: > I agree with what has been said, but would like to clarify that Cluster > and remote actors will probably not work yet. You could use untyped actors > for everything crossing remote boundaries but I guess it

[akka-user] Akka-Typed on a new project?

I read the blog for coexistence of typed actors with the current ecosystem. This looks very promising. I infer that a new project can be based upon the Akka-Typed API and use the adapter to integrate with unsupported modules like Akka-Cluster

Re: [akka-user] State Replication in ORMultiMap

tries. Separate top level >> entries cannot be updated atomically together. >> >> The only way I can read it is that in your case the entire map with 5000 >> entries will be replicated. >> >> Thanks, >> Michał >> >> >> On 18/06/17 18:00,

[akka-user] State Replication in ORMultiMap

Suppose there is an ORMultiMap with 5 keys, each pointing to an ORSet of size 1000 items. Given that ORSet is a delta-CRDT, which one of the following happens on ORMultiMap.addBinding("a", 4) operation: 1. Entire map with 5000 entries will be replicated. 2. Only the delta of the ORSet (against

Re: [akka-user] [Akka-Http] Consuming request entity multiple times

tire > thing is loaded. So such payload can be materialized twice. > > We hope to make this more configurable in the future, and help with those > scenarios even more. Hope this helps. > >  > > On Apr 11, 2017 00:06, "Mushtaq Ahmed" <mushta...@gmail.com&

Re: [akka-user] [Akka-Http] Consuming request entity multiple times

Ok, my test data was very small. If I increase the content of the uploaded data I do see the exception of multiple materialization. Thanks. On Mon, Apr 10, 2017 at 7:18 PM, Mushtaq Ahmed <mushta...@gmail.com> wrote: > Hello! > > I am uploading a file using fileUpload directive

[akka-user] [Akka-Http] Consuming request entity multiple times

Hello! I am uploading a file using fileUpload directive to an akka-http server. On server side once I get handle to the streaming request entity, I am able to successfully materialize the stream *multiple* times. How is it possible? Where does the data for the second materialization come from?

Re: [akka-user] Cluster Singleton Migration

ial package containing (among other things) code to support > this. > > Hope this helps > > - Arno > > Am 03.04.2017 um 17:19 schrieb Mushtaq Ahmed: > > Hello! > > > > Doc on cluster singleton > > <http://doc.akka.io/docs/akka/2.5.0-RC2/scala/cluster-singlet

[akka-user] Cluster Singleton Migration

Hello! Doc on cluster singleton mention that even in case of JVM crash, singletons will be successfully started on other nodes: "The cluster failure detector will notice when oldest node becomes unreachable due to things

[akka-user] Is Auto-Downing ok in this situation?

Hello! We are using these 2 services built on top akka-cluster: - distributed data: keeps service registry - singletons: used for death watching and auto unregistering actorRefs from registry Note that, there is no "persistent" state in singletons. Also, it should be ok even if more than one