Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
galene
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
galene
Commits
4b8a509a
Commit
4b8a509a
authored
Jan 05, 2021
by
Antonin Décimo
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix typos.
parent
fb30fe3b
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
6 deletions
+6
-6
README.PROTOCOL
README.PROTOCOL
+6
-6
No files found.
README.PROTOCOL
View file @
4b8a509a
# Galène's protocol
Galène
's
uses a symmetric, asynchronous protocol. In client-server
Galène uses a symmetric, asynchronous protocol. In client-server
usage, some messages are only sent in the client to server or in the
server to client direction.
## Message syntax
All messages are sent as JSON objects. All fields exc
t
ept `type` are
All messages are sent as JSON objects. All fields except `type` are
optional; however, there are some fields that are common across multiple
message types.
...
...
@@ -16,7 +16,7 @@ message types.
- `source`, the client-id of the originating client;
- `username`, the username of the originating client;
- `dest`, the client-id of the destination client;
- `privileged`, set by the server to indicate that the orignating client
- `privileged`, set by the server to indicate that the orig
i
nating client
had the `op` privilege at the time it sent the message.
## Data structures
...
...
@@ -36,7 +36,7 @@ that do not originate messages (servers) do not need to be assigned an id.
### Stream
A stream is a set of related tracks. It is identified by an id, an opaque
string. Streams in Galène are unid
e
rectional. A stream is carried by
string. Streams in Galène are unid
i
rectional. A stream is carried by
exactly one peer connection (PC) (multiple streams in a single PC are not
allowed). The offerer is also the RTP sender (i.e. all tracks sent by the
offerer are of type `sendonly`).
...
...
@@ -91,7 +91,7 @@ The `join` message requests that the sender join or leave a group:
When the sender has effectively joined the group, the peer will send
a 'joined' message of kind 'join'; it may then send a 'joined' message of
kind 'change' at any time, in order to inform the client of a change in
its permissions or in the recommen
t
ed RTC configuration.
its permissions or in the recommen
d
ed RTC configuration.
```javascript
{
...
...
@@ -178,7 +178,7 @@ an answer.
}
```
Both peers may then tricke ICE candidates with `ice` messages.
Both peers may then trick
l
e ICE candidates with `ice` messages.
```javascript
{
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment