=doc add lots of documentation about java-side routing API, some detail and further examples still missing

This commit is contained in:
Johannes Rudolph 2015-07-10 19:10:29 +02:00
parent 11d98a6593
commit ab38c36cba
20 changed files with 384 additions and 50 deletions

View file

@ -1,4 +1,8 @@
.. _client-side-websocket-support:
Client-Side WebSocket Support
=============================
TODO
Not yet implemented see 17275_.
.. _17275: https://github.com/akka/akka/issues/17275

View file

@ -8,7 +8,7 @@ with a browser is of course also in scope it is not the primary focus of Akka HT
Akka HTTP follows a rather open design and many times offers several different API levels for "doing the same thing".
You get to pick the API level of abstraction that is most suitable for your application.
This means that, if you have trouble achieving something using a high-level API, there's a good chance that you can get
it done with a low-level API, which offers more flexibility but might require you do write more application code.
it done with a low-level API, which offers more flexibility but might require you to write more application code.
Akka HTTP is structured into several modules:

View file

@ -1,3 +1,5 @@
.. _server-side-websocket-support-scala:
Server-Side WebSocket Support
=============================