Yes transferring files would make sense and the name of the xep kinda indicates that this might be the purpose. However the XEP goes on describing itself as a way to communicate all kind of URIs. And I have seen clients doing this in the wild (=when ever the user enters and sends some kind of Uri the client would generate a xoob tag)
On Mar 8, 2018 10:25, "Christian Schudt" <christian.sch...@gmx.de> wrote: > > > However I'm not really sure what the intended purpose of this XEP is > > and if we still have a use case for that purpose. > > I understood the purpose as follows: > > a) You upload some file to a server (nowadays you could also use XEP-363). > b) You send a message to a contact with XEP-0066. > c) Contact downloads the uploaded file. > > The advantage over SI File Transfer is that a file can be sent also in > offline case. > > The end user experience should be the same for all methods of file > transfer (SI, Jingle, OOB): > - Inform the receiver about an incoming file. > - Receiver can choose to accept it. > - It should be transparent to the user, if the sender used SI, Jingle or > OOB, e.g. if the file is streamed from an URL (XEP-0066) or from the sender > directly. > > TL;DR: The purpose is/was to transfer files in case the receiver is > offline. > > -- Christian > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > _______________________________________________ >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
