Looks like there's something for spray:
http://github.com/gettyimages/spray-swagger
I imagine there's nothing for Akka HTTP, seeing as it's not even officially
released yet.
--
Read the docs: http://akka.io/docs/
Check the FAQ:
Hi Nicolau,
Your description is not weird at all—ForkJoinPool's Worker threads will
scan for work when they have none of their own, which they do for about 2
seconds, and if they can't find work they'll decommission themselves.
Note that the default configuration for Akka needs to be tuned for
What is the most current implementation of Akka based asynchronous file I/O
out there? It seems akka-stream 1.0-RC3 still only has synchronous reading,
and drexin's akka-io-file github repo is more than one year old. Is there
no highly-experimental official async file IO library out there?
Nevermind :-)
I found the information I need about 40 minutes into Dr. Kuhn's talk
http://www.typesafe.com/resources/video/introducing-reactive-streams
Sorry to post an unnecessary question
P
--
Read the docs: http://akka.io/docs/
Check the FAQ:
Hi
I have to do a class cast to ge able to get a typed outlet from a flow that
I used in a FlowGraph.
1. I'm wondering if I'm using the API wrong below, can I get the outlet
in a different way?
2. Other suggestions for improvement apart from the single line is
welcome, perhaps my
On Sun, Jul 12, 2015 at 1:18 PM, Magnus Andersson
magnus.anders...@mollyware.se wrote:
Hi
I have to do a class cast to ge able to get a typed outlet from a flow
that I used in a FlowGraph.
1. I'm wondering if I'm using the API wrong below, can I get the
outlet in a different way?
Tracked as ticket: https://github.com/akka/akka/issues/17970
On Sat, Jul 11, 2015 at 11:51 PM, Konrad Malawski
konrad.malaw...@typesafe.com wrote:
Hi Sam,
Yes, interesting catch - we do not publish scaladocs as a jar.
I guess we did not bump into this previously since many Scala devs
Hi all,
I'm trying to migrate from Spray to Akka-HTTP and I'm failing to be able to
compile this most basic of examples:
http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0-RC4/scala/http/routing-dsl/index.html
The API for bindAndHandle must have changed because I have a `Route`
Hi Austin,
On Saturday, July 11, 2015 at 11:22:44 AM UTC+2, Austin Guest wrote:
(1) The test for the hello route fails because the actual response is an
internal server error. (Despite the fact that this isn't true running the
live code!) And I get the following error messages:
That's
Do you have the ActorMaterializer as an implicit value?
implicit val materializer = ActorMaterializer()
On Sunday, July 12, 2015 at 7:58:49 AM UTC-6, Sam Halliday wrote:
There seems to be some magical implicit conversion going on here, if I add
def flow: Flow[HttpRequest, HttpResponse,
That message was pretty crazy, so I wanted to give some follow-up. I made
some changes to my system, and now I was able to reach 100% CPU utilization
most of the time. I am creating this map-reduce framework while at the same
time using Spark to solve the same problem, and I believe I got a 40%
Hello, I hope this is the correct group for this question...
I have an existing pipe-line process written in Actor using the Work
Pulling pattern.
http://www.michaelpollmeier.com/akka-work-pulling-pattern/
The first stage of my pipeline is a database query written in Slick. The
result is
12 matches
Mail list logo
