public_mirrors
/
godot-demo-projects
mirror of https://github.com/godotengine/godot-demo-projects.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
godot-demo-projects/networking/webrtc_signaling
History
Hugo Locurcio fe6103256a
Allow hiDPI in all demos that support multiple resolutions 
This is required to benefit from crisp display on hiDPI monitors.
This also fixes issues related to fullscreen and input handling
when using an hiDPI display on Windows.
 		2020-10-01 00:56:12 +02:00
..
client Many tweaks thanks to IAmActuallyCthulhu 2020-06-28 13:19:13 -04:00
demo Many tweaks thanks to IAmActuallyCthulhu 2020-06-28 13:19:13 -04:00
server Many tweaks thanks to IAmActuallyCthulhu 2020-06-28 13:19:13 -04:00
server_node Remove trailing space characters in the formatting script 2020-06-21 23:00:13 -04:00
.gitignore
…
README.md Link to the asset library from the README of each demo 2020-09-10 15:37:10 -04:00
project.godot Allow hiDPI in all demos that support multiple resolutions 2020-10-01 00:56:12 +02:00

README.md

A WebSocket signaling server/client for WebRTC.

This demo is devided in 4 parts:

  • The server folder contains the signaling server implementation written in GDScript (so it can be run by a game server running Godot)
  • The server_node folder contains the signaling server implementation written in Node.js (if you don't plan to run a game server but only match-making).
  • The client part contains the client implementation in GDScript.
    • Itself divided into raw protocol and WebRTCMultiplayer handling.
  • The demo contains a small app that uses it.

NOTE: You must extract the latest version of the WebRTC GDNative plugin in the project folder to run from desktop.

Check out this demo on the asset library: https://godotengine.org/asset-library/asset/537

Protocol

The protocol is text based, and composed by a command and possibly multiple payload arguments, each separated by a new line.

Messages without payload must still end with a newline and are the following:

  • J: (or J: <ROOM>), must be sent by client immediately after connection to get a lobby assigned or join a known one. This messages is also sent by server back to the client to notify assigned lobby, or simply a successful join.
  • I: <ID>, sent by server to identify the client when it joins a room.
  • N: <ID>, sent by server to notify new peers in the same lobby.
  • D: <ID>, sent by server to notify when a peer in the same lobby disconnects.
  • S: , sent by client to seal the lobby (only the client that created it is allowed to seal a lobby).

When a lobby is sealed, no new client will be able to join, and the lobby will be destroyed (and clients disconnected) after 10 seconds.

Messages with payload (used to transfer WebRTC parameters) are:

  • O: <ID>, used to send an offer.
  • A: <ID>, used to send an answer.
  • C: <ID>, used to send a candidate.

When sending the parameter, a client will set <ID> as the destination peer, the server will replace it with the id of the sending peer, and rely it to the proper destination.