moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-24 02:02:16 -05:00
Code Issues Releases Wiki Activity

inbox/fsn: New revision; Add upload-finished state

Browse Source
This commit is contained in:
Linus Jahn 2018-08-21 16:22:27 +02:00
parent e3b0861628
commit 2dd716068c
No known key found for this signature in database
GPG Key ID: 4663231A91A1E27B
1 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
inbox/fsn.xml
View File

@ -27,6 +27,12 @@
<email>lnj@kaidan.im</email> <email>lnj@kaidan.im</email>
<jid>lnj@kaidan.im</jid> <jid>lnj@kaidan.im</jid>
</author> </author>
<revision>
<version>0.0.4</version>
<date>2018-08-21</date>
<initials>lnj</initials>
<remark><p>Add upload-finished state, minor improvements.</p></remark>
</revision>
<revision> <revision>
<version>0.0.3</version> <version>0.0.3</version>
<date>2018-07-20</date> <date>2018-07-20</date>
@ -105,17 +111,17 @@
</message> </message>
]]></example> ]]></example>
<p>Bernardo has taken a good picture for sending and has started uploading, now. The same notification is also used when the image existed before and there were no process of creating it.</p> <p>Bernardo has taken a good picture for sending and has started uploading, now. The same notification is also used when the image existed before and there were no process of creating it.</p>
<p>The 'progress' attribute has to be in the range of zero (0) and one (1). With other words the bytes sent divided by the total bytes. Generally the progress SHOULD NOT have more than two digits after the decimal point since the exact uploading status isn't important. Also there SHOULD be no more progress updates than once per second.</p> <p>The client SHOULD include a 'progress' attribute. It MUST be in the range of zero (0) and one (1). This value represents the bytes already sent divided by the total bytes. Generally it is not necessary to include more than two digits after the decimal point since the exact uploading status is not important. Clients MUST NOT send progress updates more often than once per second.</p>
<p>The 'type' attribute equals the 'type' attribute by the &lt;creating/&gt; element.</p> <p>The 'type' attribute equals the 'type' attribute by the &lt;creating/&gt; element.</p>
<example caption="User has finished the file upload"><![CDATA[ <example caption="User has finished the file upload"><![CDATA[
<message <message
from='bernardo@shakespeare.lit/pda' from='bernardo@shakespeare.lit/pda'
to='francisco@shakespeare.lit' to='francisco@shakespeare.lit'
type='chat'> type='chat'>
... <upload-finished xmlns='urn:xmpp:fsn:0'>
</message> </message>
]]></example> ]]></example>
<p>The file upload has succeeded and Bernardo sends the link to the file as defined in &xep0385; or another possible way. A notification that the file upload has finished is not sent, instead the recipient's client MUST recoginze the incoming media share and reset the state for this user.</p> <p>The file upload has succeeded. Now Bernardo can send the file sharing message as in &xep0385; or another file sharing protocol. Francisco's client MUST clear the previous &lt;uploading&gt; notification. The &lt;upload-finished/&gt; notification itself SHOULD NOT be displayed to the user.</p>
<example caption="User aborts the file upload"><![CDATA[ <example caption="User aborts the file upload"><![CDATA[
<message <message
from='bernardo@shakespeare.lit/pda' from='bernardo@shakespeare.lit/pda'