On Donnerstag, 24. August 2017 11:38:12 CEST Jonas Wielicki wrote:
> Version 0.18.2 of XEP-0234 (Jingle File Transfer) has been released.
>
> Abstract:
> This specification defines a Jingle application type for transferring
> a file from one entity to another. The protocol provides a modular
> fra
Version 0.18.3 of XEP-0234 (Jingle File Transfer) has been released.
Abstract:
This specification defines a Jingle application type for transferring
a file from one entity to another. The protocol provides a modular
framework that enables the exchange of information about the file to
be transferre
Version 0.18.2 of XEP-0234 (Jingle File Transfer) has been released.
Abstract:
This specification defines a Jingle application type for transferring
a file from one entity to another. The protocol provides a modular
framework that enables the exchange of information about the file to
be transferre
Version 0.18.0 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
a file from one entity to another. The protocol provides a modular framework
that enables the exchange of information about the file to be transfer
Version 0.17.2 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
a file from one entity to another. The protocol provides a modular framework
that enables the exchange of information about the file to be transfer
Version 0.17.1 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
a file from one entity to another. The protocol provides a modular framework
that enables the exchange of information about the file to be transfer
Version 0.17 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
a file from one entity to another. The protocol provides a modular framework
that enables the exchange of information about the file to be transferre
[...]
> using a transport-info message as described under Communicating the
> Hash.
So I make slide text about spec bugs and notice another bug:
transport-info -> session-info
On 8/12/14, 2:14 AM, Philipp Hancke wrote:
Am 12.08.2014 um 01:08 schrieb XMPP Extensions Editor:
Version 0.16 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for
transferring a file from one entity to another. The protocol pr
Am 12.08.2014 um 01:08 schrieb XMPP Extensions Editor:
Version 0.16 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
a file from one entity to another. The protocol provides a modular framework
that enables th
Version 0.16 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
a file from one entity to another. The protocol provides a modular framework
that enables the exchange of information about the file to be transferre
Version 0.15 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
files between two entities. The protocol provides a modular framework that
enables the exchange of information about the file to be transferred as we
Version 0.14 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
files between two entities. The protocol provides a modular framework that
enables the exchange of information about the file to be transferred as we
Version 0.13 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
files between two entities. The protocol provides a modular framework that
enables the exchange of information about the file to be transferred as we
While running a git diff, I discovered this version, which I'd last
modified back in early September. I figured I might as well push it out
(further fixes might be on the way soon).
On 1/5/11 12:19 PM, XMPP Extensions Editor wrote:
> Version 0.12 of XEP-0234 (Jingle File Transfer) has been release
Version 0.12 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
files between two entities. The protocol provides a modular framework that
enables the exchange of information about the file to be transferred as we
Version 0.11 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
files between two entities. The protocol provides a modular framework that
enables the exchange of information about the file to be transferred as we
On 2/11/10 8:04 PM, Jiří Zárevúcky wrote:
> Peter Saint-Andre píše v Čt 11. 02. 2010 v 19:42 -0700:
>> On 2/11/10 5:29 PM, Jiří Zárevúcky wrote:
>>> XMPP Extensions Editor píše v Čt 11. 02. 2010 v 18:06 -0600:
Version 0.10 of XEP-0234 (Jingle File Transfer) has been released.
Abstrac
Peter Saint-Andre píše v Čt 11. 02. 2010 v 19:42 -0700:
> On 2/11/10 5:29 PM, Jiří Zárevúcky wrote:
> > XMPP Extensions Editor píše v Čt 11. 02. 2010 v 18:06 -0600:
> >> Version 0.10 of XEP-0234 (Jingle File Transfer) has been released.
> >>
> >> Abstract: This specification defines a Jingle appli
On 2/11/10 5:29 PM, Jiří Zárevúcky wrote:
> XMPP Extensions Editor píše v Čt 11. 02. 2010 v 18:06 -0600:
>> Version 0.10 of XEP-0234 (Jingle File Transfer) has been released.
>>
>> Abstract: This specification defines a Jingle application type for
>> transferring files between two entities. The pr
XMPP Extensions Editor píše v Čt 11. 02. 2010 v 18:06 -0600:
> Version 0.10 of XEP-0234 (Jingle File Transfer) has been released.
>
> Abstract: This specification defines a Jingle application type for
> transferring files between two entities. The protocol provides a modular
> framework that ena
Version 0.10 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
files between two entities. The protocol provides a modular framework that
enables the exchange of information about the file to be transferred as we
Version 0.9 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
files between two entities. The protocol provides a modular framework that
enables the exchange of information about the file to be transferred as wel
Version 0.9 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
files between two entities. The protocol provides a modular framework that
enables the exchange of information about the file to be transferred as wel
Version 0.8 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
files between two entities. The protocol provides a modular framework that
enables the exchange of information about the file to be transferred as wel
Version 0.7 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
files between two entities. The protocol provides a modular framework that
enables the exchange of information about the file to be transferred as wel
Version 0.5 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
files between two entities. The protocol provides a modular framework that
enables the exchange of information about the file to be transferred as wel
On 06/04/2008 9:23 PM, Tim Julien wrote:
Could you perhaps refrain from top-posting? It makes the conversation
hard to follow. :)
> The message flow in section 2 (i.e., "happy path") seems good. Only
> question I would have is maybe wrap the bytestream / ibb negotiation
> messages in jingle tran
The message flow in section 2 (i.e., "happy path") seems good. Only
question I would have is maybe wrap the bytestream / ibb negotiation
messages in jingle transport-info messages. But I can see an argument
against that if the goal is to allow existing implementations to reuse
as much code as po
On 06/04/2008 4:49 PM, XMPP Extensions Editor wrote:
> Version 0.4 of XEP-0234 (Jingle File Transfer) has been released.
>
> Abstract: This specification defines a Jingle application type for
> transferring files between two entities. The protocol provides a
> modular framework that enables the ex
Version 0.4 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
files between two entities. The protocol provides a modular framework that
enables the exchange of information about the file to be transferred as wel
On 06/04/2008 10:08 AM, Tim Julien wrote:
> Peter Saint-Andre wrote:
>> On 05/30/2008 12:14 PM, Tim Julien wrote:
>>> One of the first things I'm going to want to do is add ice-udp (we have
>>> a reliable UDP impl) as a transport
>>
>> Isn't reliable UDP different from UDP? Or would you just negot
Peter Saint-Andre wrote:
On 05/30/2008 12:14 PM, Tim Julien wrote:
One of the first things I'm going to want to do is add ice-udp (we have
a reliable UDP impl) as a transport
Isn't reliable UDP different from UDP? Or would you just negotiate
ice-udp and if your UDP stack provides reliable UDP
On 05/30/2008 12:14 PM, Tim Julien wrote:
> One of the first things I'm going to want to do is add ice-udp (we have
> a reliable UDP impl) as a transport
Isn't reliable UDP different from UDP? Or would you just negotiate
ice-udp and if your UDP stack provides reliable UDP that would just fall
out
XMPP Extensions Editor wrote:
> Version 0.3 of XEP-0234 (Jingle File Transfer) has been released.
>
> URL: http://www.xmpp.org/extensions/xep-0234.html
The caption of example 12 is wrong, the initiator acknowledges
session-accept.
Dirk
--
Only Irish coffee provides in a single glass all four e
One of the first things I'm going to want to do is add ice-udp (we have
a reliable UDP impl) as a transport (and ice-tcp when we get that spec).
Do you envision those negotiations occurring after session-accept, like
Socks5 and IBB in this spec, or before session-accept like in jingle
audio /
Version 0.3 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
files between two entities. The protocol provides a modular framework that
enables the exchange of information about the file to be transferred as wel
On 05/29/2008 9:39 AM, Tim Julien wrote:
> Peter Saint-Andre wrote:
>> On 05/21/2008 1:18 PM, Tim Julien wrote:
>>> So, I'm confused about some of the transport negotiation stuff.
>>
>> It was sketched out rather quickly and probably needs more work.
>>
>>> In first scenario (section 3.1) the negot
Peter Saint-Andre wrote:
On 05/21/2008 1:18 PM, Tim Julien wrote:
So, I'm confused about some of the transport negotiation stuff.
It was sketched out rather quickly and probably needs more work.
In first scenario (section 3.1) the negotiation occurs after
session-accept - which is counter to
On 05/21/2008 1:18 PM, Tim Julien wrote:
> So, I'm confused about some of the transport negotiation stuff.
It was sketched out rather quickly and probably needs more work.
> In first scenario (section 3.1) the negotiation occurs after
> session-accept - which is counter to every Jingle spec that
So, I'm confused about some of the transport negotiation stuff.
In first scenario (section 3.1) the negotiation occurs after
session-accept - which is counter to every Jingle spec that has come out
so far: typically both and are negotiated as a
pre-requisite to session-accept and going into
Version 0.2 of XEP-0234 (Jingle File Transfer) has been released.
Abstract: This specification defines a Jingle application type for transferring
files between two entities. The protocol provides a modular framework that
enables the exchange of information about the file to be transferred as wel
42 matches
Mail list logo
