Re: [Telepathy] New channel request/announcement/dispatch interfaces

2008-04-15 Thread Simon McVittie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 14 Apr 2008 at 12:31:59 -0700, Ted Gould wrote: On Fri, 2008-04-11 at 12:41 +0100, Alban Crequy wrote: Le Thu, 10 Apr 2008 13:18:14 -0700, Ted Gould [EMAIL PROTECTED] a écrit : Plus the low level protocol could be SXE on Jabber, or

Re: [Telepathy] New channel request/announcement/dispatch interfaces

2008-04-15 Thread Ted Gould
On Tue, 2008-04-15 at 12:26 +0100, Simon McVittie wrote: On Mon, 14 Apr 2008 at 12:31:59 -0700, Ted Gould wrote: Sure, I understand. SXE has the same issues that Abicollab, and I actually like the protocol we used in Inkboard better than both of them. But, my goal there is to help SXE get

Re: [Telepathy] New channel request/announcement/dispatch interfaces

2008-04-11 Thread Alban Crequy
Le Thu, 10 Apr 2008 13:18:14 -0700, Ted Gould [EMAIL PROTECTED] a écrit : On Thu, 2008-04-10 at 10:06 -0700, Ted Gould wrote: I like this idea. I'm not sure if you're familiar with SXE by the Jabber folks, but I think it'd be an interesting spec to use as a model for how this stuff works.

Re: [Telepathy] New channel request/announcement/dispatch interfaces

2008-04-10 Thread Simon McVittie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 20 Mar 2008 at 13:28:19 +, Simon McVittie wrote: Rob and I have come up with the following design: * channels are not necessarily unique per (channel type, handle type, handle) any more - necessary for proper support of XMPP message

Re: [Telepathy] New channel request/announcement/dispatch interfaces

2008-04-10 Thread Ted Gould
On Thu, 2008-04-10 at 15:51 +0100, Simon McVittie wrote: Originally, I thought that the way forward was to have an object representing a bundle of channels. However, I'm now leaning more towards having secondary channels optionally point to a main channel - this would simplify dispatching to: