Hi Feyyaz,
I'm thinking what you'd have to do to stay within your organization's
required JEE environment is to create a servlet that could feed messages to
a Source.actorRef or Source.queue. based on whether you could use the
servlet async API, or need to use the venerable synchronous servlet API
Matt is correct, Akka HTTP is a complete server implementation, all the way
down the sockets, through parsing and rendering headers, lifecycle
management etc etc.
It does so in a fully streaming manner as well, which is it’s strong point.
Embedding Akka HTTP inside a servlet container sells it sho
If I am not mistaken Akka HTTP has its own HTTP server layer that it uses
(when you do Http().bind(..)). You can find more details in the Core Server
API section of the docs. It discusses in some detail what's going on under
the hood and how Akka's HTTP layer is, in my view, essentially a
repla
Hi all,
Regarding this topic, are there more details about this, or more then just
"*completely
negates all the benefits that Akka HTTP*" ?
thanks!
On Tuesday, 14 April 2015 15:49:19 UTC+2, Jas wrote:
>
> is there an example showing how to integrate servlet container with
> akka-http? i'm curr
