Hi Martin!
We haven't looked that close at protobuf yet (we don't use this for
remoting purposes, only for persistence), and we needed something that was
as simple as possible (i.e. departed from our regular data expressed as
case class-approach as little as possible), and also was fully
Hi,
I have a similar problem. I am using a custom serializer for serializing a
snapshot. (extended from akka.serialization.Serializer):
akka {
actor {
serializers {
customSerializer = com.handler.util.CustomSerializer
}
serialization-bindings {
Hi Roland,
sorry for the delay:
On Tuesday, May 13, 2014 9:11:58 AM UTC+2, rkuhn wrote:
Hi Giovanni,
13 maj 2014 kl. 08:49 skrev Giovanni Ruggiero
giovanni...@eligotech.comjavascript:
:
On Saturday, May 10, 2014 3:30:42 PM UTC+2, rkuhn wrote:
10 maj 2014 kl. 10:35 skrev Giovanni
Ha! That's helpful! I thought about using intermediate message object, but
copy is a better way. Thanks!
On Tuesday, May 20, 2014 6:24:47 AM UTC-4, Martynas Mickevičius wrote:
You should have fields of your case class immutable. Then you can pass it
between actors completing the fields as it
Akka users,
How do those of you who are using Akka with Java write immutable message
classes with collections?
Thanks
Heiko
--
Heiko Seeberger
Twitter: @hseeberger
Blog: blog.heikoseeberger.name
--
Read the docs: http://akka.io/docs/
Check the FAQ:
I am trying to integrate Spring with Akka,
using http://doc.akka.io/docs/akka-modules/1.3.1/modules/spring.html.
I would like to know if the above integration is specific to 1.3.1 release
or does it work with Akka's latest release.
This is my akka version
dependency
Hi
to me it sounds like you are modelling something like a pipeline per
request. In addition to what Martynas has suggested, you may want to get
the EA version
of Akka in Action. They describe a couple of design patterns by
translating quite common Enterprise Integration patterns to Akka.
Nice, that will probably be useful for more people!
Regards,
Roland
19 maj 2014 kl. 16:11 skrev Raman Gupta rocketra...@gmail.com:
Not yet... I'll see if I can do this over the next week or so.
On Saturday, May 17, 2014 2:34:50 PM UTC-4, Jakub Kahovec wrote:
Hi Raman,
I'd interested to
19 maj 2014 kl. 18:18 skrev delasoul michael.ham...@gmx.at:
Hello,
good catch - we are running in this situation in the moment as well - some of
our sharded actors register to a Cluster Pub-Sub topic
when started - when getting rebalanced or when a node crashes the sharded
actor is not
I defined some message with protobuffer and using them for message,In java
,no case class,and hand writing nearly kill me
在 2014年5月20日星期二UTC+8下午10时38分38秒，Heiko Seeberger写道：
Akka users,
How do those of you who are using Akka with Java write immutable message
classes with collections?
Hi Alex,
I have filed the ticket for Processor’s removal
(https://github.com/akka/akka/issues/15230), which also talks about Channel
since that was only needed to contain the side-effecting replay nature of
command sourced processors. Your description below is rather terse, so it is
not fully
I am using the persistent channel as a durable queue,and for it was not
recommend ,I switch to redis .
在 2014年5月21日星期三UTC+8上午2时32分38秒，rkuhn写道：
Hi Alex,
I have filed the ticket for Processor’s removal (
https://github.com/akka/akka/issues/15230), which also talks about
Channel since that
For what it's worth, this has also come up quite a few times in the #akka
IRC channel on Freenode. It might be worth adding a fairly obvious not on
the main docs page (http://akka.io/docs/) indicating that snapshots should
only be used by those wanting to live on the edge (it seems in the Scala
Hello,
I checkout the latest source of Akka and ran into many errors in sbt when
downloading dependencies(it happened only to some of them):
akka deliver
[info] Updating
{file:/Users/cfchou/Project/02_scala_libs/akka/}akka-sample-camel-scala...
[warn] module not found:
Hi,
this is a known problem in sbt-0.13.5-RC1. We are waiting for RC5 which
should fix this issue. In the meantime you should be fine using 0.13.2.
Just clean your ivy cache after downgrading.
On Tue, May 20, 2014 at 9:36 PM, Chifeng Chou cfc...@gmail.com wrote:
Hello,
I checkout the latest
Hi Odd,
that is a very good question: I was operating under the premise that
EventsourcedProcessor is used quite a bit by now and renaming it might not be
met with unlimited enthusiasm. The replacement for PersistentChannel will need
to be named differently since the “persistent” in the name
Hi.
First of all, thanks for your time reading this.
I'm working with an Akka cluster and I don't understand a peculiar effect
I'm observing. If I send 70 simultaneous messages (and for each message a
callback resend the message again) everything works fine. But if I try the
same with 100
For sure... Akka version 2.3.2!
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the
Hello!
I have the following setup:
- actor TaskScheduler, registered through ClusterReceptionist like this:
def main(args: Array[String]) {
val port = if (args.isEmpty) 0 else args(0)
val config =
ConfigFactory.parseString(sakka.remote.netty.tcp.port=$port).
+1 for PersistentActor
Heiko
On Tue, May 20, 2014 at 10:50 PM, Roland Kuhn goo...@rkuhn.info wrote:
Hi Odd,
that is a very good question: I was operating under the premise that
EventsourcedProcessor is used quite a bit by now and renaming it might not
be met with unlimited enthusiasm. The
20 matches
Mail list logo
