Hi Konrad,
Thanks a lot, these are excellent examples. I'm sure that's pretty common
pattern, so putting it in docs seems like a good idea.
In my case Sink.onComplete was enough (simply as a replecement for
Sink.ignore). However it was kind of tricky to move MaterializedMap to
outer scope for
This thread in spray-user [0] got me curious about akka-http's current and
future usage of the low level mechanisms. I'm not very familiar with
akka-io underpinnings, but does it use a similar single thread for even
notifications off of the socket? If so I assume that akka-http eventually
gets
I have raised https://github.com/akka/akka/issues/16893
It has an isolated repro case.
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
---
You
Hello,
I'm would like to build a web server to handle a high load of requests
(many thousands per seconds). I'm trying to figure out if akka-http is a
good candidate for that.
At first sight, I would guess so since it comes from Spray which definitely
offers good performance under high load.
HI Giovanni,
On Mon, Feb 16, 2015 at 11:31 PM, Giovanni Alberto Caporaletti
paradi...@gmail.com wrote:
You're absolutely right about the future not representing an already
running computation. But it's not a blueprint. If a see a future, I take
for granted that something will happen sooner
Hi Jean!
Without skimming your actual benchmarks let me reply right away – Akka HTTP is
definitely a great long-term candidate for what you’re after,
but(!) currently we have not yet performance tuned the underlying streams
architecture. It is expected that 1.0-M3 is not crazy fast. We do plan
