| Summary: | TP Farstream should provide a helper to set handler_capabilities | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Nicolas Dufresne <nicolas> |
| Component: | tp-farstream | Assignee: | Olivier Crête <olivier.crete> |
| Status: | RESOLVED WONTFIX | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | git master | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
(In reply to comment #0) > tp_base_client_add_handler_capabilities_varargs (client, > TF_FUTURE_IFACE_CHANNEL_TYPE_CALL "/video/h264", > NULL); Why wouldn't this go into tp-glib? Handler capabilities aren't restricted to just a/v codecs anyway. (In reply to comment #1) > (In reply to comment #0) > > tp_base_client_add_handler_capabilities_varargs (client, > > TF_FUTURE_IFACE_CHANNEL_TYPE_CALL "/video/h264", > > NULL); > > Why wouldn't this go into tp-glib? Handler capabilities aren't restricted to > just a/v codecs anyway. I misread, ignore me, sorry! I'm tempted to make this wontfix. 1. Having multiple handlers doesn't work with #47296 2. Even if we had this in tp-fs, it would mean that all the handlers would need to be ran before an incoming call to figure out which tokens they support. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
TP Farstream should provide a helper that transform the supported audio/video codec and transmitters into Telepathy capabilities. E.g. tp_base_client_add_handler_capabilities_varargs (client, TF_FUTURE_IFACE_CHANNEL_TYPE_CALL "/video/h264", NULL);