[jdev] Re: New MSN-t in the works
trejkaz at xaoza.net
Thu Aug 12 21:29:38 CDT 2004
On Fri, 13 Aug 2004 10:07, James Bunton wrote:
> Right now I have the new transport working. It shouldn't be too hard to
> adapt for AOL/ICQ, all the legacy protocol code is in one directory, so
> that can be swapped out. I've still got a few critical things.
> Disco/Browse/Agents (think it's still worth supporting the last two?), as
> well as in band registration and groupchat.
> Oh yeah, I wanted to ask. Has anybody got any good ideas for a better way
> to do Jabber<->MSN groupchat? The MSN protocol makes no separation between
> groupchats and ordinary chats, and extra people can be invited into a room
> at any time. So the only way I can think of handling it is..
> * MSN contact invites a new person into the room.
> * MSN-t notices, converts the room to a conference and sends Jabber user an
> invite to the virtual conference room
> * Jabber joins the conference and receives any buffered events with
> * If the Jabber user doesn't join the conference within (maybe 3 minutes?)
> then they get a message from the transport with a transcript of the
> conference room so far, and they leave the conference on the MSN side.
> Any objections/suggestions?
That already sounds infinitely better than what we currently have. :-)
Does the MSN protocol really give the user no way to reject an invite? I
always thought it was odd that an MSN user was able to get me into a
conference even if I didn't want to be there. I always figured it would be
better if it sent an invite, and only joined me to the real conference when I
joined to the transported one. :-/
'Every sufficiently advanced technology is indistinguishable from magic' -
Arthur C Clarke
'Every sufficiently advanced magic is indistinguishable from technology' - Tom
Email: Trejkaz Xaoza <trejkaz at xaoza.net>
Web site: http://xaoza.net/trejkaz/
Jabber ID: trejkaz at jabber.xaoza.net
GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F A62C B8C7 BC8B 037E EA73
More information about the JDev