Seems to add escaping not needed to SockJS communication

[mkotsbak]

In Chrome websocket monitoring, it seems like the messages sent through the websocket looks like this:

["{"req":{"path":["shared","Api","echo"],"args":{"s":"\"Test fra klient med client i val\""}},"id":1}"]

a["{"res":"\"Received on server: Test fra klient med client i val\"","id":1}"]

Why are all "-s escaped? I'm not sure if it is this library or SockJS that does it.

It is sort of ok if both the client and the server is using the library, but if there are some other manually created clients written in another programming language, it would be hard to replicate the protocol.

Maybe it instead could use the JSON-RPC protocol?: http://en.wikipedia.org/wiki/JSON-RPC

[OlivierBlanvillain]

Why are all "-s escaped? I'm not sure if it is this library or SockJS that does it.

This is related to the way remote procedure call are handled. The RPCWrapper uses Autowire and uPickle, which I think can be tuned to use whatever RPC representation / serialization format you like.

[mkotsbak]

Would it be possible to use Js.Value instead of Strring in RpcWrapper.scala as proposed in the references issue in Autowire above?