Paolo Angioletti

@andre77 @hkothari @JeremyRodon I believe there is nothing broken neither in jawampa nor in Poloniex. I'd like to give some detailed insights about the WAMP protocol but I couldn't do...

My understanding of transport and sessions is that they are separate entities operating at different levels. The former carries messages between peers to open/close one or more of the latter....

I also believe the best solution is to make **loose validation** the default behaviour for routers. I'm just enhancing my [angiolep/akka-wamp](https://github.com/angiolep/akka-wamp) router to apply _strict validation_ only when explicitly configured...

Section **10.1.1. Incorrect URIs** of specs doesn't make clear what a **strict router** shall reply if client sends the following HELLO message: `[1,"my..REALM",{"roles":{"publisher":{}}}]` I suppose an ABORT with `"wamp.error.invalid_uri"` reason...

Cool, +1

Hi asciuu, thanks very much for using akka-wamp Please send emails to [email protected] next time. That's the account I read the most of the time. Feel free to file a...

Having the following registration in place: ``` scala def sum(a: Int, b: Int) = a + b val registration: Future[Registration] = session.flatMap( _.register( procedure = "myapp.procedure.sum", handler = sum _...

Implementing this enhancement may require to split the ``core`` module into three separate modules: ``core``, ``router`` and ``client``