Hi Josh,
We didn't yet publish/document our actor / cluster protocols very
explicitly.
We'd like to do this at some point, so perhaps other impls could talk to an
akka cluster – no plans on when this might happen though.
This plays into an interesting story about exposing actors as services –
Hello Yann,
There is not “nulling” involved. The PersistentRepr acts as envelope for
your payload (your message), and adds some metadata to it (persistenceId
etc).
See details here:
https://github.com/akka/akka/blob/master/akka-persistence/src/main/scala/akka/persistence/Persistent.scala#L191
We
Hi Lawrence!
I think what you're looking for is the other overload of the Logging apply
method:
val log = Logging(system, classOf[MyCustomerLogger])
I hope this helps, happy hakking!
On Fri, Aug 1, 2014 at 2:03 PM, Lawrence Wagerfield
lawre...@dmz.wagerfield.com wrote:
I would like to
Both ways are perfectly fine, pick one and try to be consistent with it in
your codebase :-)
More info in the docs:
http://doc.akka.io/docs/akka/snapshot/scala/actors.html#initialization-patterns
On Fri, Aug 1, 2014 at 9:42 AM, Tim Pigden tim.pig...@optrak.com wrote:
I'm using actors to
Hi,
I'm currently trying to implement some kind of supervision in my app. Some
context first : I have a controller actor dispatching files to parse when
processor actor is done with his previous file. Of course I need to
bootstrap the processing chain when application starts. My file
Hi,
I'm currently trying to implement some kind of supervision in my app. Some
context first : I have a controller actor dispatching files to parse when
processor actor is done with his previous file. Of course I need to
bootstrap the processing chain when application starts. My file
Hey Odd,
This looks promising. Thanks for passing along.
Greg
On Sunday, August 3, 2014 3:04:27 AM UTC-7, Odd Möller wrote:
Hi Greg
I have a prototype implementation of an Akka extension that uses
persistence to save scheduler state:
Implementing a fully distributed actor system on Arduino's is going to be
challenging given the limited resources available. I would suggest looking more
at an ARM-based platform, such as TI's Launchpad. But realistically, the Pi or
a similar platform (Beagleboard, Cubieboard, etc.) might be an
It worked in a sense that Akka started local instances as well as remote
ones. The problem is that nr-of-instances number of actors were started on
each host. I am wondering if there is away to control the number of
instances on each host?
On Friday, August 1, 2014 11:28:57 AM UTC-4, √ wrote:
This is something i've been wondering myself too.
In particular, I think there would be a LOT of potential awesome/benefit in
being able to integrate Rails with Akka; be it JVM akka using ruby/rails as
actors (since there tend to be a LOT more gem's published for random API's,
etc), or a Rails
Within the JVM it’s dead easy to integrate between languages… :-) Random fact:
I’ve actually used Scala code from JRuby on Rails some years ago. An outline on
how to do this is on my blog:
http://www.blog.project13.pl/index.php/fun/1497/teaching-jruby-talk-with-scala-on-rails/
And as you can
11 matches
Mail list logo
