Fix compiler error/warnings

This commit is contained in:
Jakob Borg
2015-11-04 17:33:49 +00:00
parent d5d0bd946b
commit b2f00c5994
2 changed files with 7 additions and 6 deletions
+1 -1
View File
@@ -33,7 +33,7 @@ certificate was presented, status ``403`` (Forbidden) is returned. If the
posted data doesn't conform to the expected format, ``400`` (Bad Request) is posted data doesn't conform to the expected format, ``400`` (Bad Request) is
returned. returned.
In successfull responses, the server may return a ``Reannounce-After"``header In successfull responses, the server may return a ``Reannounce-After`` header
containing the number of seconds after which the client should perform a new containing the number of seconds after which the client should perform a new
announcement. announcement.
+6 -5
View File
@@ -124,11 +124,12 @@ Session mode
The first and only message the client sends in the session mode is the The first and only message the client sends in the session mode is the
SessionInvitation message which contains the session key identifying which SessionInvitation message which contains the session key identifying which
session you are trying to join. session you are trying to join. The relay responds with one of the following
.. The relay responds with one of the following Response messages: Response messages:
1. ResponseNotFound - Session key is invalid
2. ResponseAlreadyConnected - Session is full (both sides already connected) 1. ResponseNotFound - Session key is invalid
3. ResponseSuccess - You have successfully joined the session 2. ResponseAlreadyConnected - Session is full (both sides already connected)
3. ResponseSuccess - You have successfully joined the session
After the successful response, all the bytes written and received will be After the successful response, all the bytes written and received will be
relayed between the two devices in the session directly. relayed between the two devices in the session directly.