![]() The JSON-API can't _really_ use regular http requests because this server then has to do a lot of multi-threading nonsense. For the sake of simplicity for myself and others that try to write their own FC compliant servers: the rtc server(for now) only takes in websocket requests, and attemptes to discern servers from users connections for event handling |
||
---|---|---|
.. | ||
.gitignore | ||
auth.js | ||
main.js | ||
package-lock.json | ||
package.json | ||
peers.js | ||
readme.md |
RTC WebSocket Server
This server is to be used only if the json-api
server is compiled with the rtc
feature.
If you run this server without that feature in the json-api
then this will never get updates from the API and thus be completely 100% useless.
Configuration
This server runs on port 5648 and is served via the ws://
protocol.
It is recommended that admins put this behind some a reverse proxy for secure web-sockets wss://
and to remove the need for specifying the port number for clients.
Command line flags
-p --port : Defaults to 5648 (suggested)