[Bug 34071] RCC should contain one RoomList entry per supported server

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=34071

--- Comment #5 from Guillaume Desmottes <guillaume.desmottes at collabora.co.uk> 2011-02-14 04:01:43 PST ---
(In reply to comment #4)
> I think the two requestable channel classes that make sense for room lists are
> "a room list with an arbitrary DNS name" and "the single default room list". If
> we want lists of suggested "nearby" room list and contact list servers, they
> should be informational properties, not part of a requestable channel class,
> IMO.

Atm Gabble has only one RCC:
({ ChannelType: RoomList, TargetHandleType: None}, [Server])

Should we have
({ ChannelType: RoomList, TargetHandleType: None}, [])
as well for the "default" case?


> Perhaps we could have a Conn.I.SuggestedServices or something, which is
> basically the same concept as Jabber disco? "These services are attached to our
> home server or recommended by our sysadmin, please offer them to the user",
> basically.

Yes that could do the job. Using an a{sv} I guess:

Conn.I.SuggestedServices = {
  'org.freedesktop.Telepathy.Channel.Type.RoomList.Server': ['server1',
'server2'],
  'org.freedesktop.Telepathy.Channel.Type.ContactSearch.Server': ['badger']
}

With the semantic that the first element in the list is the one used by
default.

My use case is basically displaying a default server in the GtkEntry allowing
user to define its own server.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.