[Telepathy] Telepathy Status

[Dafydd Harries]

Ar 09/10/2006 am 21:23, ysgrifennodd Eitan Isaacson:
> * We are right now building a vertical solution in the sense that we are
> managing accounts, connections, contacts, and incoming channels all in
> the same process. If we are truly subscribing to the telepathy way of
> life we need to redefine the goals of gossip. Telepathy dictates that
> there should be something called mission control[3] that will do all the
> background handling of connections and account settings and delegate
> actual communications to separate channel handlers, so these are some
> options I see:
> 	1. separate gossip in to two processes, mission control, and everything
> else.
> 	2. stay monolithic, and delegate unhandled channels to external
> handlers.
> 	3. size down to a roster and IM interface.
> 	4. combination of 2 and 3, be a self sustaining process with an option
> of cooperating with an MC.
> Just thought I would throw that out there and hopefully flare up some
> discussion :)

One way forward would be for Gossip to implement the MC API, and for MC to be
split into a separate component later on.

There was a lot of enthusiasm at Boston for the Telepathy port of Gossip, and
it was suggested that we propose it for inclusion in Gnome 2.18. If we want to
do this, we should do it right now -- I think the deadline for proposals is
the 13th. I personally feel this is a good idea: getting Gossip with Telepathy
support into Gnome would be a major boon to both Telepathy and Gnome. If
inclusion is rejected, we can always re-propose it for 2.20. Either way, not
having MC as a separate component should not block Gossip's adoption by Gnome.

-- 
Dafydd