[Standards-JIG] Converting a chat session into a conference
jconley at winfessor.com
Wed Jul 28 19:49:16 UTC 2004
I've been brainstorming this recently as well. In order to make this
process more automated a unique identifier for the conference room
should be generated. A GUID, or something based on a hash of the JIDs
of the original participants would work fine. In an effort to keep
clients simple we could also add something into MUC to request a new
unique room from the component just like we do with resource binding.
I like the continue addition to the invite.
> -----Original Message-----
> From: Ian Paterson [mailto:ian.paterson at clientside.co.uk]
> Sent: Wednesday, July 28, 2004 12:39 PM
> To: Jabber protocol discussion list
> Cc: stpeter at jabber.org
> Subject: RE: [Standards-JIG] Converting a chat session into a
> When two people, who have been chatting privately, decide to include
> person in their discussion, then they must perform several steps in
> move the discussion into a conference room. Many users consider these
> too complicated.
> If JEP-45's invite protocol featured the optional new <continue/>
> defined below, then the process could be automated by the clients.
> When an <invite/> that includes a <continue/> element is received,
> of opening a new conference window, the client can convert its
> private chat window into a conference window and display the previous
> discussion history in the room.
> For example, when Hecate's client receives the stanza below it
> converts its Crone1 private chat window into a Darkcave conference
> <message from='darkcave at macbeth.shakespeare.lit'
> to='hecate at shakespeare.lit'>
> <x xmlns='http://jabber.org/protocol/muc#user'>
> <invite from='crone1 at shakespeare.lit'>
> <reason>I'm going to bring Hag66 into this discussion.</reason>
> Standards-JIG mailing list
> Standards-JIG at jabber.org
More information about the Standards