Need a way for clients to know what kinds of channel can be handled.
Submitted by Will Thompson @wjt
Assigned to Telepathy bugs list
Description
Currently, a client can look at a Connection's RequestableChannelClasses property to figure out what kinds of channels it can request. But this is not necessarily useful:
- A CM might support channels with THT: Room, but that's not to say that there's a client installed that can handle them. So a contact list UI might look at RCC, see that rooms are available, and have a bunch of room-related UI which is actually useless because any channels that get created will be terminated with extreme prejudice by the dispatcher.
- A client can see that Gabble supports 1-1 stream tubes, but that doesn't help it figure out what services to offer when you right-click a contact. It should be able to have a "Play Tic-Tac-Tube" option.
This information is already present in the form of the union of all activatable and running clients' HandlerChannelFilter properties, applied to the CM's requestable channel classes. So maybe extra spec is unnecessary.
There's also a localization issue here: every contact list needs to know what the human-readable description of service=tictactube is.