JSON-RPC mode

[CodeShellDev]

Hey there 👋,
I would like to know what exactly the json-rpc mode does / changes?
What are its upsides and downsides?
How exactly is the data inside of the socket structured? Same as usual, or is it different to for example normal mode? What endpoints are affected and which are still the same?
I have never ever used json-rpc, so I really don‘t know anything about it (maybe it is similar to grpc?).

Thanks in advance!

[bbernhard]

In normal/native mode you need to periodically call the receive endpoint for normal operation. In json-rpc mode changes are automatically fetched from the Signal Server. The API for all the modes is the same, except for the receive endpoint. In json-rpc mode this is a websocket endpoint.

[CodeShellDev]

Ok, thanks!

[CodeShellDev]

Does the request to the websocket also use the /v1/receive endpoint? And what do you need to send as params to the websocket endpoint to initialize?

[bbernhard]

Yes, it uses the exact same endpoint - the payload that is returned is also the same. The only difference is, that the endpoint is a HTTP GET in the native/normal mode and a websocket connection in json-rpc mode.

If you want to establish a websocket connection you can e.g use the wscat commandline tool:

wscat -c 127.0.0.1:8080/v1/receive/<registeredSignalNumber> --show-ping-pong --slash