... | ... | @@ -20,9 +20,9 @@ The messages exchanged between two contacts referring to a given blog constitute |
|
|
|
|
|
The protocol uses five message types.
|
|
|
|
|
|
**0: INVITE** - Sent by either party to start or restart a session. The message body is a BDF list with four elements: `messageType` (int), `previousMessageId` (unique ID or null), `descriptor` (list), and `message` (string or null).
|
|
|
**0: INVITE** - Sent by either party to start or restart a session. The message body is a BDF list with four elements: `messageType` (int), `previousMessageId` (unique ID or null), `descriptor` (list), and `text` (string or null).
|
|
|
|
|
|
`previousMessageId` is the ID of the previous message in this session, if any. `descriptor` is the [descriptor of the blog](Blog-Client#group-identifiers) being shared. `message` is an optional message from the inviter to the invitee. The blog ID must be calculated from the descriptor, as it is used by subsequent messages in the session.
|
|
|
`previousMessageId` is the ID of the previous message in this session, if any. `descriptor` is the [descriptor of the blog](Blog-Client#group-identifiers) being shared. `text` is an optional message from the inviter to the invitee. The blog ID must be calculated from the descriptor, as it is used by subsequent messages in the session.
|
|
|
|
|
|
The sender sets the blog's visibility to VISIBLE when sending an invite message.
|
|
|
|
... | ... | |