From 09b115f5a628fcc0c7941306843df6e30094af1b Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Fri, 11 Oct 2013 12:46:37 +0100 Subject: [PATCH 6/7] Add FileCollection to FileTransfer interface The implementation in Gabble hasn't changed since 2010, so it's de facto stable. We should either spec it or delete it. --- spec/Channel_Type_File_Transfer.xml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/spec/Channel_Type_File_Transfer.xml b/spec/Channel_Type_File_Transfer.xml index f50b963..420f6fa 100644 --- a/spec/Channel_Type_File_Transfer.xml +++ b/spec/Channel_Type_File_Transfer.xml @@ -579,6 +579,35 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. + + + +

The collection of files to which this channel belongs, + or the empty string if this channel does not belong to + a collection of files.

+ +

A channel's FileCollection property can never change.

+ +

At least on GTalk and apparently also on iChat the user can + send a set of files to a contact and that contact can then + pick and choose which files to actually receive.

+ +

The CM should emit all new FT channels belonging to one collection + at the same time. UIs supporting this feature can then + bundle all these channels together in some way, and show a + nice UI. UIs not supporting it will treat them as separate + transfers, which is not great but a reasonable fallback.

+ +

No mechanism is currently defined to indicate whether the UI + should expect any more files in the same collection. UIs + SHOULD assume that more file transfers may be added to a + collection. It is possible that a "no more channels in this + collection" indication will be added in a future version of + this specification.

+ + + -- 1.8.4.rc3