| Summary: | Specify that PreferredHandler should trump HandlerChannelFilter | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Will Thompson <will> |
| Component: | tp-spec | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | Keywords: | patch |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| URL: | http://git.collabora.co.uk/?p=user/smcv/telepathy-spec-smcv.git;a=shortlog;h=refs/heads/preferred-handler-trumps-filters | ||
| Whiteboard: | specmeet? | ||
| i915 platform: | i915 features: | ||
| Bug Depends on: | 23651 | ||
| Bug Blocks: | 25302 | ||
|
Description
Will Thompson
2009-09-17 15:13:27 UTC
Please mention in the rationale that this also allows a client to become the handler for a channel that it requests, without being forced to be a candidate to handle *every* outgoing channel of that type. The semantic change looks good to me, but I don't want this in the spec until it's true in our reference implementation, so I'm setting the corresponding MC bug as a blocker. I'd be willing to have this in 0.19.0. Since we only have one practical implementation of a ChannelDispatcher, and this functionality only works in the latest version of it, it may be worth explicitly noting "In telepathy-mission-control, this works in version 5.3.2 or later." I've hijacked this branch to get it into 0.19.0. See: http://people.freedesktop.org/~smcv/telepathy-spec-preferred_handler_trumps_filters/spec/org.freedesktop.Telepathy.ChannelDispatcher.html#org.freedesktop.Telepathy.ChannelDispatcher.CreateChannel Fixed in git, will be in 0.19.0 |
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.