On 2015-08-26 16:36, Evgeny Khramtsov wrote: > Wed, 19 Aug 2015 15:44:30 +0000 (UTC) > XMPP Extensions Editor <edi...@xmpp.org> wrote: > >> The XMPP Extensions Editor has received a proposal for a new XEP. >> >> Title: Jingle HTTP Transport Method >> >> Abstract: This specification defines two Jingle transport methods for >> establishing HTTP connections for either uploading or downloading >> data. >> >> URL: http://xmpp.org/extensions/inbox/jingle-http-transport.html >> >> The XMPP Council will decide in the next two weeks whether to accept >> this proposal as an official XEP. >> > > I have several question on the XEP: > > 1) How is it possible to get several URLs during HTTP Upload? For > example, an HTTP server may generate previews and return > them with the main URL. This is done in a lot of pics hostings and is > very handy for a client.
Didn't Jingle File Transfer support transfer of multiple files? > 2) How is it possible to offer HTTP Download (see 7.1) with multiple > files and some of those are thumbnails? So, for example, a receiving > entity sees a thumbnail first and downloads the original content if she > likes it. As for sending a thumbnail, there is a XEP for that: http://xmpp.org/extensions/xep-0264.html > 3) How this XEP can be combined with MUC? Let's say a client did HTTP > Upload, how will it share the URL in MUC? Will it use procedures from > 7.1 directly to MUC room jid? > 4) How this XEP can be used when a user wants to share an HTTP Uploaded > URI with an offline contact? > > I don't see this XEP resolves any of these. Some of those are things that could be described in different XEPs that may or may not have been written yet. -- Kim "Zash" Alvefur
signature.asc
Description: OpenPGP digital signature
