From 6b53252c7f79023d77a1002d00308b5b38d838ba Mon Sep 17 00:00:00 2001 From: Emmanuel Gil Peyrot Date: Sun, 7 Aug 2016 21:41:42 +0100 Subject: [PATCH] XEP-0329: Remove unnecessary whitespace around examples --- xep-0329.xml | 56 +++++++++++++++------------------------------------- 1 file changed, 16 insertions(+), 40 deletions(-) diff --git a/xep-0329.xml b/xep-0329.xml index 55ddba53..163361ee 100644 --- a/xep-0329.xml +++ b/xep-0329.xml @@ -71,19 +71,15 @@

If a requesting entity wishes to know what files are being shared by an offering entity, it can do so by sending the following query:

- - - -]]> - +]]>

If the offering entity wishes to share files with the requesting entity, it may respond with a list of shared folders. It MUST not include any files in this response.

- - - -]]> - +]]>

if the offering entity has no files to offer

- - - -]]> - +]]>

Requesting the list of files and directories within a directory.

- - - -]]> - +]]>

When replying with a list of files, the offering entity can choose to either reply with verbose information on the file using the file attributes defined by &xep0234; or it may reply only with the 'name' attribute, which is required and MUST be included in every response.

It is RECOMENDED, when the list files to be sent is small, that a verbose response be made (in order to avoid going back and forth requesting information), and that a non-verbose reponse be made otherwise. This recomendation is made to save bandwidth.

- - - -]]> - +]]>

If the requesting entity wants to get detailed information about a file. It can do so by providing its full path.

- - - -]]> - - -]]> + 1000 - -]]> - +]]> @@ -186,8 +165,7 @@

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.

- - - -]]> - +]]>

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.