From 98f7f1523c99533c56aa3af13766bc380c531b54 Mon Sep 17 00:00:00 2001 From: Lance Stout Date: Thu, 7 Jan 2016 09:21:21 -0800 Subject: [PATCH] INBOX Jingle HTTP Transport: Update signaling of upload completions. --- inbox/jingle-http-transport.xml | 66 +++++++++++++-------------------- 1 file changed, 26 insertions(+), 40 deletions(-) diff --git a/inbox/jingle-http-transport.xml b/inbox/jingle-http-transport.xml index f0871682..eeb18d7e 100644 --- a/inbox/jingle-http-transport.xml +++ b/inbox/jingle-http-transport.xml @@ -22,6 +22,12 @@ NOT_YET_ASSIGNED &lance; + + 0.0.2 + 2016-01-07 + ljts +

Renamed <uploaded/> to <completed/>, and made it a child of the <transport/> element in transport-info events.

+
0.0.1 2015-07-30 @@ -200,15 +206,19 @@

A common case for using http-upload is to delegate the storage of the uploaded data to an external hosting service, which means that the receiver might not have the direct ability to know when the uploaded data is ready.

-

As such, when an upload transfer is used, the party uploading content SHOULD signal when the upload has completed by sending a Jingle session-info event that includes a <uploaded/> element qualified by the 'urn:xmpp:transports:http:info:0' namespace and SHOULD include 'creator' and 'name' attributes identifying the content for which the upload was completed.

+

As such, when an upload transfer is used, the party uploading content SHOULD signal when the upload has completed by sending a Jingle transport-info event that specifies the content for which uploading has completed, and includes a <transport/> element qualified by the 'urn:xmpp:jingle:transports:http:upload:0' namespace, which in turn contains a <completed /> element.

- + action='transport-info'> + + + + + ]]>
@@ -365,9 +375,13 @@ to='juliet@capulet.lit/balcony' type='set'> - + + + + + ]]> @@ -427,9 +441,13 @@ to='romeo@montague.lit/orchard' type='set'> - + + + + + ]]> @@ -556,6 +574,7 @@ + @@ -578,39 +597,6 @@ -]]> - - - - - - - - - - - - - - - - - - - - - - - - - ]]>