Hi ric
thanks for your answer. I guess my problem is not really with akka http
(spray is fine) but with akka streams. I don't want to start my project
with rx and then migrate to akka streams.
Let's leave akka-http out of the question and reformulate: should I start
using akka-streams right
I am sending heavy rate of messages to the actor that updates it's state
for (i -0 to 10){
persistentActor ! Cmd(foo+i)
}
and using the persistAsync like this
val receiveCommand: Receive = {
case Cmd(data) =
persistAsync(Evt(s${data}-${numEvents}))(updateState)
case snap =
According to
http://doc.akka.io/docs/akka/snapshot/scala/persistence.html#Relationship_between_deliver_and_confirmDelivery
: A function can be created to map your own messageId to deliveryId, which
may come from your own domain model. This function must keep track of which
messageId have been
I have upgraded to 2.3.9 it have now been running for 5 days, without any
problems.
On 28 January 2015 at 11:50, Idar Borlaug idar.borl...@gmail.com wrote:
I know, we have a few problems with upgradeing to 2.3.9. (we might wait
until eventstore has a cluster connector for java)
The only
Generally there are 2 ways to design for this problem:
Once you have an actor reference, you can send things to it. So you can
simply do this:
targetActorRef ! myThing
When the actor is done with the processing, it will call:
myThing.myMethod
This design is OK when the target actor is very
this is now past due: https://github.com/akka/akka/milestones/2.4.0
can someone in the know please update us on the akka 2.4.0 release date?
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives:
Our clustered app has a cluster singleton actor that constructs a Cluster
instance, and also subscribes to cluster events.
If you ask it, What are the current nodes? it uses cluster.state.members.
I.e., simplified, something like:
val cluster = Cluster(context.system)
override def
After alot of head scratching I came to same conclusions as you. It's good
to see somebody else having the same ideas.
On Wednesday, 4 February 2015 21:06:11 UTC, Ngoc Dao wrote:
Generally there are 2 ways to design for this problem:
Once you have an actor reference, you can send things to
I found some nice example showing integration of netty with akka on github.
This is what I'm looking at https://github.com/gibffe/fuse
specifically
https://github.com/gibffe/fuse/blob/master/src/main/java/com/sulaco/fuse/netty/FuseChannelHandler.java
Its embarrassingly simple :)
On Tuesday, 3
Dear users
I find the semantics of defer confusing.
I thought defer was the same as persist, except the given message was not
persisted. Now today, when a bug got me to read the doc again, it states
that defer has the same semantics as persistAsync.
My first thought was that defer should be
10 matches
Mail list logo
