[Standards-JIG] Chat Session Negotiation
jean-louis.seguineau at laposte.net
Wed Jan 4 18:17:02 UTC 2006
This is a good idea as well. I don't see that anything in the JEP goes
against multiple re-negotiation as long as for example the <thread/> remain
Maybe I am mis-interpreting the post, but I would stick to using only
<message/> as a transport. The re-negotiation in relation to certain
presence changes should in my opinion be left to a particular client/gateway
implementation and expressed using messages. Adding <presence/> to the mix
would in my opinion only introduce complexity, and add difficulty when
mapping with other protocols.
Date: Wed, 4 Jan 2006 12:32:09 -0500
From: Thomas Charron <twaffle at gmail.com>
Subject: Re: [Standards-JIG] Chat Session Negotiation
To: Jabber protocol discussion list <standards-jig at jabber.org>
<30dfe2a80601040932y45be52e4ye8fb91b36ff5bdd7 at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Allo Peter, long time no see.. :-)
I just rejoined most of the lists, and you'll probrably hear some more in
the future.. ;-)
I just had a comment on this particular JEP that occured to me while I was
reading thru it.
There should probrably also be a way to renegotiate an existing
conversation to use different parameters then the ones that existed at the
initiation of the chat session. In SIP, for example, this is handled by
renegotiating capabilities by quite literally re INVITE with the new
paramaters using the same session. This could be handled pretty much the
same way w/ JEP-0155, but there's one issue. Clients connections are, for
the most part, considered stateless. If I disconnect from one client, and
reconnect with another, the chat session 'state' information is unknown to
the new client.
Perhaps a presence change off offline at any point should trigger an
automatic renegotiation of params, or at least confirmation of params?
On 1/3/06, Peter Saint-Andre <stpeter at jabber.org> wrote:
> OK, I updated JEP-0155 accordingly.
> The SIP mapping requires more text, but it's a start.
More information about the Standards