Akka Http is not a webframework. It's an Akka based implementation of asynchronous requests available since servlet 3.0 Each request will have own actor. Actor will live until async request is processed and completed or time is out. Processing of async request is divided by different unit of work. All these work units will be processed one by one, however Actor may receive one of the javax.servlet.AsyncEvent between. In case of Error, Timeout or Complete events actor will stop processing and shutdown. So all work units left will be dropped.
Async context has been divided on different scopes. Each scope is a synchronous unit of work
-
Request scope. Expected to be the heaviest scope. All request related logic shhould go here
-
Response scope. Light scope for putting request result in response
-
Callback scope. Simple callback function. Passes
TRUEwhen response succeeded,FALSEotherwise.
We need scope to receive async event messages in between. Thus will allow us to avoid various exceptions
For example you may get response time out exception or response already completed, etc.
Also you can avoid odd operations when requrest has expired.
RequestMethod was removed. However you are able to use HttpServletRequest/Response directly.
- Using old akka 1.3 akka-mist
def receive = {
case get: Get =>
get.response.setContentType("text/html")
val html =
<html>
<body>
<h1>Hello World</h1>
<h3>endpoint actor</h3>
</body>
</html>
get.OK(html)
}- Using new akka 2.0 akka-http
def receive = {
case req: HttpServletRequest =>
// doing some heavy work here
//will be called for completing request
val func = (res: HttpServletResponse) => {
res.getWriter.write(
<html>
<body>
<h1>Hello World</h1>
<h3>endpoint actor</h3>
</body>
</html>.toString())
res.getWriter.close()
// our callback whether response succeed
(b: Boolean) => println("SUCCEED: " + b)
}
//passing func to AsyncActor, created for this AsyncContext
sender ! Complete(func)
}We are not using Endpoint hierarchy from akka-mist. We have single EndpointsActor instead where you can find/add/remove endpoint in runtime,
you can find appropriate commands in Endpoints.scala.
It's possible to retrieve this actor via HttpExtension HttpExtension(system).endpoints or direclty system.actorFor("/user/endpoints")
MistSettings were moved to HttpExtension with other common stuff. Http properties will be defined per ActorSystem.
AkkaMistServlet was renamed to AkkaHttpServlet, AkkaMistFilter to AkkaHttpFilter. Both of them extend trait AkkaHttp
From Akka Migration Guide
In v1.3 the default name of the configuration file was akka.conf. In v2.0 the default name is application.conf.
Akka Http properties has been removed from akka-reference.conf (akka.conf).
So Akka Mist has own reference.conf.
However some of the properties were removed from mist at all, same happened with related functionality.
Most of the properties you can retrieve from HttpExtension.scala.
Extension mechanism is new, added in Akka 2.0
root-actor-id = "_httproot"toendpoints-actor-name = endpoints- path of the actor to use for receiving and adding endpoints, call 'actorFor(/user/endpoints)'
system-name = http- name of the system used in servletendpoint-retrieval-timeout = 500- HTTP 404 if no endpoint retrieved within defined timeout (ms), should be less then timeoutlog-http-config-on-init = off- Log akka.http configuration at INFO level on Servlet/Filter init.
hostname = "localhost"port = 9998filters = ["akka.security.AkkaSecurityFilterFactory"]resource-packages = []authenticator = "N/A"connection-close = truekerberos.servicePrincipal = "N/A"kerberos.keyTabLocation = "N/A"kerberos.kerberosDebug = "N/A"kerberos.realm = ""