Bug 30963 - A way for Handlers to match channels based on their Accounts
Summary: A way for Handlers to match channels based on their Accounts
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-spec (show other bugs)
Version: unspecified
Hardware: Other All
: medium enhancement
Assignee: Vivek Dasmohapatra
QA Contact: Telepathy bugs list
URL: http://git.collabora.co.uk/?p=user/pt...
Whiteboard: stalled
Keywords: patch
Depends on: 30964
Blocks:
  Show dependency treegraph
 
Reported: 2010-10-18 06:47 UTC by Senko Rasic
Modified: 2019-12-03 20:22 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Senko Rasic 2010-10-18 06:47:29 UTC
It would be useful if a handler could match channels based on their accounts. Eg. irc-optimized client could say 'I want to handle all text channels on accounts that use protocol "irc".'

A way to do this could be filters matching Account object path and/or properties. To make this more useful, a read-only Protocol property could be added to Account - although it's encoded in the Account object path, having a separate property is useful for matching.
Comment 1 Senko Rasic 2010-10-18 07:04:57 UTC
Reassigning to Vivek for reviewing and setting severity to enhancement.
Comment 2 Simon McVittie 2010-10-18 07:16:46 UTC
The semantics in terms of "and" and "or" need to be clearer. I assume the semantics are meant to be:

handle every channel where
    both
        either
            the account matches AccountFilter[0]
        or
            the account matches AccountFilter[1]
        ...
    and
        either
            the channel matches HandlerChannelFilter[0]
        or
            the channel matches HandlerChannelFilter[1]
        ...

I'm not sure that this should be on Handler: how about a new Client.I.AccountFiltering that could apply to any class of Client?
Comment 3 GitLab Migration User 2019-12-03 20:22:42 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/86.


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.