From d767706ab2053de56ff3b30c6e0f6f9cb1ab2b2a Mon Sep 17 00:00:00 2001 From: Emmanuel Gil Peyrot Date: Sun, 7 Aug 2016 21:49:32 +0100 Subject: [PATCH] XEP-0329: Add a wrapper iq around the Jingle session initiation example --- xep-0329.xml | 31 ++++++++++++++++++------------- 1 file changed, 18 insertions(+), 13 deletions(-) diff --git a/xep-0329.xml b/xep-0329.xml index 5fe53c7e..2911b290 100644 --- a/xep-0329.xml +++ b/xep-0329.xml @@ -166,19 +166,24 @@

As it was previously discussed, when requesting detailed information about a file, only the "name" attribute is required, but it is strongly RECOMMENDED that the hash attribute be included, in order to reduce the chances of sending the wrong file. When requesting the file to be transferred using &xep0234;, the information that must be provided has to identify the file uniquely. It is then RECOMMENDED that when requesting a file, the full path of the file in the shared folder be included in the "name" attribute.

- - - - pics/test4.png - 10740 - - - -]]> + + + + + + pics/test4.png + 10740 + + + + +]]>

For the most part, discovering files in a MUC is exactly the same as what has been described in this document. However, it is RECOMMENDED that a participant in a MUC should have a single shared folder associated with the entire room, as opposed to advertise different files to different participants of the room. This is to reduce the complexity of the client software. Also, due to volatile nature of the participants in a room, keeping track of permissions is more trouble than what it is worth.