wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Specification for direct-to-device messages

Browse source
This commit is contained in:
Richard van der Hoff 2016-09-27 12:17:05 +01:00
parent 459f4b953d
commit ccd7bb32d5
6 changed files with 262 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

24
specification/server_server_api.rst
View file

@ -974,3 +974,27 @@ The list of join candidates is a list of server names that are likely to hold
the given room; these are servers that the requesting server may wish to use as
resident servers as part of the remote join handshake. This list may or may not
include the server answering the query.
Store-and-forward messages
--------------------------
.. TODO: add modules to the federation spec and make this a module
The server API for store-and-forward messaging is based on the following
EDU. There are no PDUs or Federation Queries involved.
Each store-and-forward message should be sent to the destination server using
the following EDU::
EDU type: m.direct_to_device
Content keys:
sender: user ID of the sender
type: event type for the message
message_id: unique id for the message: used for idempotence
messages: The messages to send. A map from user ID, to a map from device ID
to message body. The device ID may also be *, meaning all known devices
for the user.