I'm doing a flatMapMerge something like this:
val stream = Source(channelMonths)
.flatMapMerge(10, channelMonth => {
..Sources.intervalsForChannelMonth(channelMonth, ...)
})
I'm implementing some monitoring using alsoTo to send stream elements to a
monitoring actor whic
If your Akka program creates the process (for example, using ProcessBuilder),
then you can capture the output and do whatever you want with it, including
routing it into an Akka stream.
If the process is started by some other means then it would be harder - you
would need to capture the outpu
I came up with this code:
http://pastebin.com/LNTCvebe
But beware until now I have only be using akka with java. It is my first
try on using scala!
As a side note : I could not figure out how to match an non-empty list in
receive?
Many Greetings
John
Am Sonntag, 20. März 2016 14:31:51 UT
Something very simple which come to my mind is to mapAsync to the ask
pattern and then do a "schedule of 10 secs" if the element is an empty list.
Am Sonntag, 20. März 2016 14:31:51 UTC+1 schrieb john@gmail.com:
>
> val input = Source(List(List(1, 2, 3), List(1, 2, 3), List(),
> List(),L
val input = Source(List(List(1, 2, 3), List(1, 2, 3), List(),
List(),List(),List(),List(1, 2, 3))
1) Process input. for example input.via(throttleFlow).mapConcat(t => t)
where throttleFlow show do the *following:*
2) If element of source has size > 0 pass it immediately downstream.
3) Or
Are you sure you are approaching the problem from the best angle? Akka
gives you a guarantee that the execution of actor code is single threaded,
so each time a message is processed, the code has an "exclusive lock" on
the actor's internal state (quotation marks because there is actually no
loc
On Sun, Mar 13, 2016 at 7:12 PM, Владимир Морозов
wrote:
> If two Player's actors live in two different remote actor systems - how
> safely transfer item from one player to other (read transactionally or
> guaranteed)
>
We don't do distributed transactions, they're the root of all evil in
distri
Camel is still very good at what it does IMHO.
It's been around for a long time, and perhaps it shows in some aspects, however
the number of
integrations it provides is really huge, so that's still a great thing about it.
Akka-Camel has not really seen much chances in the last years, but having t
New Java API is comign in very large steps, I think the new one you'll like
a lot and come back to plain Akka :-)
On Mon, Mar 14, 2016 at 5:13 PM, Guido Medina wrote:
> Also there are other aspects you should be aware like back-pressure which
> is better handled at Akka, to be fair both teams a
Great news !
>From my experience current remoting ( cluster that depends on it) is way to
fragile to be used in boxes that are not in the same data center, and in
such case of co-location UDP is perfectly fine.
I expect that people trying to deploy in any "enterprise" or "coroprate"
environments
I guess that I am suffering from deadlock? this post semms to apply to my
problem
http://blog.lancearlaus.com/akka/streams/scala/2015/05/27/Akka-Streams-Balancing-Buffer/
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/ak
This would be the solution I would use:
http://pastebin.com/pJVnHqcH
I am a little unsure about mat.stop() and the Supervision.stop().
Should the code work? I want to restart on every Exception thrown from any
Flow,Source,Sink of the Runnable graph
Am Freitag, 18. März 2016 11:28:23 UTC+1 sch
12 matches
Mail list logo
