RS Backpressure can piggyback on top of TCP, which means HTTP, WebSocket
and HTTP/2 support.
Besides that there's *tons* of integrations (Sources and Sinks) for
networked components.
As if that wasn't enough there's both the ReactiveSocket initiative (
http://reactivesocket.io/) as well as Apache
HOLD ON .. SERIOUSLY?!
So, do I understand correctly that the 'Reactive Manifesto' industry
coalition among leading thought leaders at Netflix, Pivotal, and Lightbend;
is for all intents and purposes -- still under construction?
Sorry; I'm just seeking straight answers on this to gauge if th
I can answered my own question here. It pretty much just came down to my
lack of knowledge around the streams API, which I hadn't used yet. Changing
the test to this works perfectly:
test("test journal backwards compatibility", EndToEndTest) {
val readJournal = PersistenceQuery(system).readJou
Hi,
I'm trying to implements a way to control a flow (start/stop), nothing was
implemented yet in the core of akka-stream
My current implementation looks like this.
trait ValveSwitch {
def open: Unit
def close: Unit
}
class Valve[A](mode: ValveMode = ValveMode.Open) extends
GraphStageWit
Thank you. That did the trick.
watch(subscriber1)
system.stop(subscriber1)
expectTerminated(subscriber1)
val subscriber2 = system.actorOf(props1, "name1") // New actor, same
name
subscriber2 ! Subscriber.GetState
val result2 = expectMsg(...something...)
On Thu,
On Thu, Oct 13, 2016 at 11:08 AM, Sebastian Piu
wrote:
> Is there any way of simulating the failure while processing, or force
> terminate the actor?
>
There is a akka.actor.Kill message that will make the Actor throw an
ActorKilledException, which will trigger supervision. The default
supervisio
Is there any way of simulating the failure while processing, or force
terminate the actor?
It if my understanding that stopping will do it after the current message
finishes right?
On Thu, 13 Oct 2016, 08:01 Patrik Nordwall,
wrote:
> The actor's name and persistenceId doesn't have to be the sam
The actor's name and persistenceId doesn't have to be the same, but if you
need that you must wait until it has been terminated before starting the
new instance
watch(subscriber1)
expectTerminated(subscriber2)
On Thu, Oct 13, 2016 at 7:10 AM, Richard Rodseth wrote:
> Thanks, but if I do this:
>
