[Telepathy] Proposed spec change: user-defined server-side groups

Robert McQueen robert.mcqueen at collabora.co.uk
Thu Oct 19 07:43:32 PDT 2006


Simon McVittie wrote:
> * User-defined groups are also channels of type ContactList, but they
>   have a new handle type CONNECTION_HANDLE_TYPE_USER_CONTACT_GROUP
>   (I might shorten that to ..._TYPE_GROUP).

++ on the shorter name :)

> * Empty user-defined groups remain open, but if you exit the connection
>   manager, they're not guaranteed to still exist after you reconnect
>   (some protocols, like XMPP, have no server-side representation of
>   empty groups). You can delete an empty group by calling its Close
>   method.

Not saying that this is wrong, but what are the merits of this versus a
group channel closing when it becomes empty on the servers where empty
groups don't really exist?

> * Channel.Close() can raise Disconnected, NetworkError or NotImplemented
>   as before, but can also raise NotAvailable. The distinction is:
>   NotImplemented means this channel can never be closed (like contact lists),
>   NotAvailable means this channel can't be closed while in its current
>   state (like non-empty user-defined groups).

Good.

> * A new group flag CHANNEL_GROUP_FLAG_ONLY_ONE_GROUP is used to mark
>   groups for which a given contact can only be in one group of this type
>   (user-defined groups should have this flag if the protocol treats
>   groups like directories rather than like tags).

Also good.

> These are implemented in a Gabble branch also available from the Merge
> Monkey.

Spec change is good to go if you make the name shorter. :)

> 	Simon

Regards,
Rob
_______________________________________________
Telepathy mailing list
Telepathy at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/telepathy



More information about the Telepathy mailing list