WebRTCPeerConnection.xml 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209
  1. <?xml version="1.0" encoding="UTF-8" ?>
  2. <class name="WebRTCPeerConnection" inherits="RefCounted" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../../doc/class.xsd">
  3. <brief_description>
  4. Interface to a WebRTC peer connection.
  5. </brief_description>
  6. <description>
  7. A WebRTC connection between the local computer and a remote peer. Provides an interface to connect, maintain and monitor the connection.
  8. Setting up a WebRTC connection between two peers may not seem a trivial task, but it can be broken down into 3 main steps:
  9. - The peer that wants to initiate the connection ([code]A[/code] from now on) creates an offer and send it to the other peer ([code]B[/code] from now on).
  10. - [code]B[/code] receives the offer, generate and answer, and sends it to [code]A[/code]).
  11. - [code]A[/code] and [code]B[/code] then generates and exchange ICE candidates with each other.
  12. After these steps, the connection should become connected. Keep on reading or look into the tutorial for more information.
  13. </description>
  14. <tutorials>
  15. </tutorials>
  16. <methods>
  17. <method name="add_ice_candidate">
  18. <return type="int" enum="Error" />
  19. <param index="0" name="media" type="String" />
  20. <param index="1" name="index" type="int" />
  21. <param index="2" name="name" type="String" />
  22. <description>
  23. Add an ice candidate generated by a remote peer (and received over the signaling server). See [signal ice_candidate_created].
  24. </description>
  25. </method>
  26. <method name="close">
  27. <return type="void" />
  28. <description>
  29. Close the peer connection and all data channels associated with it.
  30. [b]Note:[/b] You cannot reuse this object for a new connection unless you call [method initialize].
  31. </description>
  32. </method>
  33. <method name="create_data_channel">
  34. <return type="WebRTCDataChannel" />
  35. <param index="0" name="label" type="String" />
  36. <param index="1" name="options" type="Dictionary" default="{}" />
  37. <description>
  38. Returns a new [WebRTCDataChannel] (or [code]null[/code] on failure) with given [param label] and optionally configured via the [param options] dictionary. This method can only be called when the connection is in state [constant STATE_NEW].
  39. There are two ways to create a working data channel: either call [method create_data_channel] on only one of the peer and listen to [signal data_channel_received] on the other, or call [method create_data_channel] on both peers, with the same values, and the [code]"negotiated"[/code] option set to [code]true[/code].
  40. Valid [param options] are:
  41. [codeblock]
  42. {
  43. "negotiated": true, # When set to true (default off), means the channel is negotiated out of band. "id" must be set too. "data_channel_received" will not be called.
  44. "id": 1, # When "negotiated" is true this value must also be set to the same value on both peer.
  45. # Only one of maxRetransmits and maxPacketLifeTime can be specified, not both. They make the channel unreliable (but also better at real time).
  46. "maxRetransmits": 1, # Specify the maximum number of attempt the peer will make to retransmits packets if they are not acknowledged.
  47. "maxPacketLifeTime": 100, # Specify the maximum amount of time before giving up retransmitions of unacknowledged packets (in milliseconds).
  48. "ordered": true, # When in unreliable mode (i.e. either "maxRetransmits" or "maxPacketLifetime" is set), "ordered" (true by default) specify if packet ordering is to be enforced.
  49. "protocol": "my-custom-protocol", # A custom sub-protocol string for this channel.
  50. }
  51. [/codeblock]
  52. [b]Note:[/b] You must keep a reference to channels created this way, or it will be closed.
  53. </description>
  54. </method>
  55. <method name="create_offer">
  56. <return type="int" enum="Error" />
  57. <description>
  58. Creates a new SDP offer to start a WebRTC connection with a remote peer. At least one [WebRTCDataChannel] must have been created before calling this method.
  59. If this functions returns [constant OK], [signal session_description_created] will be called when the session is ready to be sent.
  60. </description>
  61. </method>
  62. <method name="get_connection_state" qualifiers="const">
  63. <return type="int" enum="WebRTCPeerConnection.ConnectionState" />
  64. <description>
  65. Returns the connection state. See [enum ConnectionState].
  66. </description>
  67. </method>
  68. <method name="get_gathering_state" qualifiers="const">
  69. <return type="int" enum="WebRTCPeerConnection.GatheringState" />
  70. <description>
  71. Returns the ICE [enum GatheringState] of the connection. This lets you detect, for example, when collection of ICE candidates has finished.
  72. </description>
  73. </method>
  74. <method name="get_signaling_state" qualifiers="const">
  75. <return type="int" enum="WebRTCPeerConnection.SignalingState" />
  76. <description>
  77. Returns the [enum SignalingState] on the local end of the connection while connecting or reconnecting to another peer.
  78. </description>
  79. </method>
  80. <method name="initialize">
  81. <return type="int" enum="Error" />
  82. <param index="0" name="configuration" type="Dictionary" default="{}" />
  83. <description>
  84. Re-initialize this peer connection, closing any previously active connection, and going back to state [constant STATE_NEW]. A dictionary of [param configuration] options can be passed to configure the peer connection.
  85. Valid [param configuration] options are:
  86. [codeblock]
  87. {
  88. "iceServers": [
  89. {
  90. "urls": [ "stun:stun.example.com:3478" ], # One or more STUN servers.
  91. },
  92. {
  93. "urls": [ "turn:turn.example.com:3478" ], # One or more TURN servers.
  94. "username": "a_username", # Optional username for the TURN server.
  95. "credential": "a_password", # Optional password for the TURN server.
  96. }
  97. ]
  98. }
  99. [/codeblock]
  100. </description>
  101. </method>
  102. <method name="poll">
  103. <return type="int" enum="Error" />
  104. <description>
  105. Call this method frequently (e.g. in [method Node._process] or [method Node._physics_process]) to properly receive signals.
  106. </description>
  107. </method>
  108. <method name="set_default_extension" qualifiers="static">
  109. <return type="void" />
  110. <param index="0" name="extension_class" type="StringName" />
  111. <description>
  112. Sets the [param extension_class] as the default [WebRTCPeerConnectionExtension] returned when creating a new [WebRTCPeerConnection].
  113. </description>
  114. </method>
  115. <method name="set_local_description">
  116. <return type="int" enum="Error" />
  117. <param index="0" name="type" type="String" />
  118. <param index="1" name="sdp" type="String" />
  119. <description>
  120. Sets the SDP description of the local peer. This should be called in response to [signal session_description_created].
  121. After calling this function the peer will start emitting [signal ice_candidate_created] (unless an [enum Error] different from [constant OK] is returned).
  122. </description>
  123. </method>
  124. <method name="set_remote_description">
  125. <return type="int" enum="Error" />
  126. <param index="0" name="type" type="String" />
  127. <param index="1" name="sdp" type="String" />
  128. <description>
  129. Sets the SDP description of the remote peer. This should be called with the values generated by a remote peer and received over the signaling server.
  130. If [param type] is [code]"offer"[/code] the peer will emit [signal session_description_created] with the appropriate answer.
  131. If [param type] is [code]"answer"[/code] the peer will start emitting [signal ice_candidate_created].
  132. </description>
  133. </method>
  134. </methods>
  135. <signals>
  136. <signal name="data_channel_received">
  137. <param index="0" name="channel" type="WebRTCDataChannel" />
  138. <description>
  139. Emitted when a new in-band channel is received, i.e. when the channel was created with [code]negotiated: false[/code] (default).
  140. The object will be an instance of [WebRTCDataChannel]. You must keep a reference of it or it will be closed automatically. See [method create_data_channel].
  141. </description>
  142. </signal>
  143. <signal name="ice_candidate_created">
  144. <param index="0" name="media" type="String" />
  145. <param index="1" name="index" type="int" />
  146. <param index="2" name="name" type="String" />
  147. <description>
  148. Emitted when a new ICE candidate has been created. The three parameters are meant to be passed to the remote peer over the signaling server.
  149. </description>
  150. </signal>
  151. <signal name="session_description_created">
  152. <param index="0" name="type" type="String" />
  153. <param index="1" name="sdp" type="String" />
  154. <description>
  155. Emitted after a successful call to [method create_offer] or [method set_remote_description] (when it generates an answer). The parameters are meant to be passed to [method set_local_description] on this object, and sent to the remote peer over the signaling server.
  156. </description>
  157. </signal>
  158. </signals>
  159. <constants>
  160. <constant name="STATE_NEW" value="0" enum="ConnectionState">
  161. The connection is new, data channels and an offer can be created in this state.
  162. </constant>
  163. <constant name="STATE_CONNECTING" value="1" enum="ConnectionState">
  164. The peer is connecting, ICE is in progress, none of the transports has failed.
  165. </constant>
  166. <constant name="STATE_CONNECTED" value="2" enum="ConnectionState">
  167. The peer is connected, all ICE transports are connected.
  168. </constant>
  169. <constant name="STATE_DISCONNECTED" value="3" enum="ConnectionState">
  170. At least one ICE transport is disconnected.
  171. </constant>
  172. <constant name="STATE_FAILED" value="4" enum="ConnectionState">
  173. One or more of the ICE transports failed.
  174. </constant>
  175. <constant name="STATE_CLOSED" value="5" enum="ConnectionState">
  176. The peer connection is closed (after calling [method close] for example).
  177. </constant>
  178. <constant name="GATHERING_STATE_NEW" value="0" enum="GatheringState">
  179. The peer connection was just created and hasn't done any networking yet.
  180. </constant>
  181. <constant name="GATHERING_STATE_GATHERING" value="1" enum="GatheringState">
  182. The ICE agent is in the process of gathering candidates for the connection.
  183. </constant>
  184. <constant name="GATHERING_STATE_COMPLETE" value="2" enum="GatheringState">
  185. The ICE agent has finished gathering candidates. If something happens that requires collecting new candidates, such as a new interface being added or the addition of a new ICE server, the state will revert to gathering to gather those candidates.
  186. </constant>
  187. <constant name="SIGNALING_STATE_STABLE" value="0" enum="SignalingState">
  188. There is no ongoing exchange of offer and answer underway. This may mean that the [WebRTCPeerConnection] is new ([constant STATE_NEW]) or that negotiation is complete and a connection has been established ([constant STATE_CONNECTED]).
  189. </constant>
  190. <constant name="SIGNALING_STATE_HAVE_LOCAL_OFFER" value="1" enum="SignalingState">
  191. The local peer has called [method set_local_description], passing in SDP representing an offer (usually created by calling [method create_offer]), and the offer has been applied successfully.
  192. </constant>
  193. <constant name="SIGNALING_STATE_HAVE_REMOTE_OFFER" value="2" enum="SignalingState">
  194. The remote peer has created an offer and used the signaling server to deliver it to the local peer, which has set the offer as the remote description by calling [method set_remote_description].
  195. </constant>
  196. <constant name="SIGNALING_STATE_HAVE_LOCAL_PRANSWER" value="3" enum="SignalingState">
  197. The offer sent by the remote peer has been applied and an answer has been created and applied by calling [method set_local_description]. This provisional answer describes the supported media formats and so forth, but may not have a complete set of ICE candidates included. Further candidates will be delivered separately later.
  198. </constant>
  199. <constant name="SIGNALING_STATE_HAVE_REMOTE_PRANSWER" value="4" enum="SignalingState">
  200. A provisional answer has been received and successfully applied in response to an offer previously sent and established by calling [method set_local_description].
  201. </constant>
  202. <constant name="SIGNALING_STATE_CLOSED" value="5" enum="SignalingState">
  203. The [WebRTCPeerConnection] has been closed.
  204. </constant>
  205. </constants>
  206. </class>