Le mercredi 19 août 2015, 15:44:30 XMPP Extensions Editor a écrit :
> 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
Wed, 26 Aug 2015 19:38:35 -0700
Lance Stout lancest...@gmail.com wrote:
To that end, I submitted an update to XEP-0264 today to get it out of
the Deferred state, allow it to use other URI types, and expand its
scope to more than just file transfer thumbnails (for example,
attaching a
Wed, 26 Aug 2015 16:48:41 +0200
Kim Alvefur z...@zash.se wrote:
Didn't Jingle File Transfer support transfer of multiple files?
OK, probably it does. But it's still unclear how this will interact
with thumbnails. As I understand several files will be rejected at the
first step (only thumbnails
On 2015-08-26 16:36, Evgeny Khramtsov wrote:
Wed, 19 Aug 2015 15:44:30 + (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
Wed, 19 Aug 2015 15:44:30 + (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
I don't see this XEP resolves any of these.
That is correct.
However, this XEP was never intended to solve those issues, in the exact same
way that no other Jingle transport (IBB, SOCKS5, ICE, raw UDP, etc) is intended
to directly solve those problems. These are things that apply to *all*
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:
