Hi Alex!
On 2/10/10 12:59 AM, Alexander Gnauck wrote:
> XEP-0206 sais:
>
>
> If the BOSH wrapper is not empty, then it SHOULD contain
> ...
> One or more complete , , and/or elements
> qualified by the 'jabber:client' namespace.
>
>
> then there is a note which sais:
>
>
> Many existing XMP
On 2/10/10 10:47 AM, Justin Karneges wrote:
> On Wednesday 10 February 2010 09:29:31 XMPP Extensions Editor wrote:
>> The XMPP Extensions Editor has received a proposal for a new XEP.
>>
>> Title: Jingle Relay Nodes
>>
>> Abstract: This documents specifies how Jingle Clients can interact with
>> Ji
On Wednesday 10 February 2010 09:29:31 XMPP Extensions Editor wrote:
> The XMPP Extensions Editor has received a proposal for a new XEP.
>
> Title: Jingle Relay Nodes
>
> Abstract: This documents specifies how Jingle Clients can interact with
> Jingle Relay Nodes Services and how XMPP entities can
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Jingle Relay Nodes
Abstract: This documents specifies how Jingle Clients can interact with Jingle
Relay Nodes Services and how XMPP entities can provide, search and list
available Jingle Relay Nodes.
URL: http://www.xmpp.
Am 03.02.2010 um 19:27 schrieb Yann Leboulanger:
Jonathan Schleifer wrote:
Am 02.02.2010 um 20:59 schrieb Yann Leboulanger:
I start encrypting the conversation (GPG or E2E).
While this is true for E2E, it indeed makes sense to store GPG-
encrypted
message encrypted. Here, the replay attack
XEP-0206 sais:
If the BOSH wrapper is not empty, then it SHOULD contain
...
One or more complete , , and/or elements
qualified by the 'jabber:client' namespace.
then there is a note which sais:
Many existing XMPP-specific implementations of BOSH clients and
connection managers do not sp
