Hi Patrik,
Thanks for the info. I saw the Google Compute Engine post only last week -
possibly when I was searching for this answer!
You mentioned the gossip interval and how the time would grow
logarithmically - are these the main two things to consider?
Is there at least a *very rough*
Hello Tim!
I think the docs should be mostly self contained - as in, if I'm in the
woods in Laponia with no WiFi, with the docs downloaded, I should be able
to figure out what I need from the docs :-)
You are very welcome to open issues and pull requests!
--
Cheers,
Konrad 'ktoso' Malawski
On Thu, Apr 24, 2014 at 11:14 AM, Tim Pigden tim.pig...@optrak.com wrote:
Are there rules for the docs?
For example - what if my searches have found an excellent blog article on
the topic? Can I reference it?
The documentation is versioned to a specific Akka version and it could be a
problem
Hi All,
I just took a quick look at the new reactive streams API and in particular
the scala DSL at
http://doc.akka.io/api/akka-stream-experimental/0.2/index.html#akka.stream.scaladsl.Flow.
Looks pretty good so far. I especially like that this is supposed to evolve
into a standard for the entire
On Thu, Apr 24, 2014 at 12:04 PM, Tim Pigden tim.pig...@optrak.com wrote:
Hi
Guidelines say not to start work until the ticket has been reviewed. Is
that necessary here?
Go ahead, guidelines are not rules. I think the purpose of that is to agree
on bigger features.
On Thursday, April
Hi,
On Wed, Apr 23, 2014 at 5:44 PM, Richard Cole richcol...@googlemail.comwrote:
I'm currently using akka to implement a basic processing workflow. My
MasterActor will receive a message that contains N number of elements
within it. At this point I can divide these elements across Y number
Hi, I'm playing around with akka-persistence, and one thing that's not
clear to me is the best way to 1) Handle the command that might create an
instance of a particular event processor (e.g. CreateOrder(...)) 2) Route
commands to the proper instance of the created eventsourced processor (e.g.
On Thu, Apr 24, 2014 at 9:37 AM, Lawrence Wagerfield
lawre...@dmz.wagerfield.com wrote:
Hi Patrik,
Thanks for the info. I saw the Google Compute Engine post only last week -
possibly when I was searching for this answer!
You mentioned the gossip interval and how the time would grow
That's fantastic, thanks!
On Thursday, April 24, 2014 3:16:09 PM UTC+1, Patrik Nordwall wrote:
On Thu, Apr 24, 2014 at 9:37 AM, Lawrence Wagerfield
lawr...@dmz.wagerfield.com javascript: wrote:
Hi Patrik,
Thanks for the info. I saw the Google Compute Engine post only last week
-
Because there are many potential implementations, we explicitly opted out
of flatMap. For now.
A minor correction: Akka Streams (Flow etc) will never become a standard
for the JVM.
The standardization effort is Reactive Streams and that is for interop
between implementations. As such it does not
I tried for the fun of it a thread.sleep 5000 prior to getting the actor
after a restart. that didn't help. Although, even if it did help I would
argue, it would just prove that there is a bug because I should need to
resort to such measures.
--
Read the docs: http://akka.io/docs/
There is an undefined amount of time it takes to traverse the actor paths
and kill the actor. The following code fails without the sleep.
Using akka 2.1.2 here fyi.
system.actorOf(Props(new Actor {
def receive = {
case hi = sender ! hi back
}
}), hi-actor)
Hi
I have done some work with Karaf and Akka, 2 years ago as part of a POC.
After all this time the project has been given a new lease of life and I am
starting on a production version of the work I initiated then. I am looking
at utilising the full JBoss Fuse stack - Karaf, Camel, Fabric8
13 matches
Mail list logo
