We're currently using akka for a variety of things, and are starting some
experiments with akka-cluster, but we've hit one roadblock.
>From the documentation on akka-cluster membership lifecycle
(http://doc.akka.io/docs/akka/2.5.4/scala/common/cluster.html#membership-lifecycle)
:
the actor
I'm working on a small layer powered by akka-http routing DSL to sort of
enforce all the RESTful APIs have the same structure.
Implementation should just have to define the URL the work on, then the
create/read/update/delete/etc.
My idea was to pass the PathMatcher into the constructor, and
/a8dd56f9c2988098e61d1e30c495ea9ed14944dd/src/main/scala/scimap/handler/ServerHandlerStage.scala
2 -
https://github.com/cretz/scimap/blob/a8dd56f9c2988098e61d1e30c495ea9ed14944dd/src/it/scala/scimap/JavaMailSpec.scala#L114
On Wednesday, July 1, 2015 at 6:55:33 AM UTC-5, Chad Selph wrote:
I tried something like
have not done this yet, I would assume you can do this with a
PushPullStage that pushes in onPull. How the state gets there to know when
to push in onPull is probably an implementation detail.
On Monday, June 29, 2015 at 5:15:53 AM UTC-5, Chad Selph wrote:
I'm currently rewriting a library I
I'm currently rewriting a library I have that previously used akka IO
pipelines. Reading through the examples of streaming IO with akka-stream
and akka-http, I've only seen examples with request - response type
protocols.
Currently, I have a BidiFlow that serializes/deserializes between
Sorry to hi-jack this 2 month old thread; but I actually had the same
problem and having it in DEBUG log isn't quite enough for me.
Basically there's a feature of my app that could use the failure mode for
diagnostics: timeout in our use-case typically means someone forgot to
open their
