Hi,
Thanks for the hint, Björn. I've been pursuing the idea and used
japi.HttpApp, but ended up with the following compilation error:
[error] found : akka.http.server.scala.Route
[error] (which expands to) akka.http.server.RequestContext = scala.
Hi,
It appears to be first step of Java routing API [1] with just a single
commit (perhaps squashed earlier to make it look so). What's Java routing
API? How is this different from Scala's one if any?
[1]
Hi Jacek,
As the name implies, japi is the java api, you’re not meant to be using those
if you’re using Scala - just use the normal scala APIs.
The Scala Routing DSL cannot be reused directly by Java since it’s using all
kinds of Scala types which simlpy do not look as nice in Java.
Akka HTTP
A few days ago I stumbled across *akka.remote.OversizedPayloadException*.
Successfully I found the solution in this user list: the problem was in
*akka.remote.netty.tcp.maximum-frame-size* config parameter which is set
to128000 bytes by default. My question is how can I reproduce this
Hey guys,
Hope you had a great break :-) Just a quick note in case you're not sure
if/when I'm around.
I'm back in PL already but off work until the 6th (as the 6th is a public
holiday in poland http://www.kalendarzswiat.pl/lista_swiat/2015).
I'm arranging some family stuffs over these days, but
Hi, hAkkers!
We're in the process of moving our distributed Akka service from the dark
ages of remoting and manual management of IPs (shudder) into the wonderful
new world of Akka Cluster.
Currently, our project is split up something like this:
- spray-frontend
- worker-1
- worker-2
I have following requirements for designing a clusterwide messaging system
1. There can be many to many relationship between topics and subscribers.
ie. one module (OSGi) in each cluster node can subscribe to more than one
topic and each topic can be subscribed to by more than one module. So,
