Bug 57721 - Allowing local tube serialization and approvers to append channel identification info. to offered tube parameters
Summary: Allowing local tube serialization and approvers to append channel identificat...
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-30 07:18 UTC by Chandni Verma
Modified: 2019-12-09 11:22 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Chandni Verma 2012-11-30 07:18:31 UTC 
How are older channels identified? Should URNs/UUIDs be used which can collide so are bad and there are users not willing to establish a whole new ID system?

I propose it should be possible for the "parameters" property of dbus-tubes to be allowed to be able to add in some more parameters (eg. local data such as path to the older channel-data-file to resume or key to some local database) before invoking the handler?

Since if the file doesn't exist, the user might want to not play the game, so searching for it is the task of the approver and re-searching in the handler to actually continue would be nothing but a repetition of approver's processing.

I haven't yet looked into how to approach this implementation or what could be the implications preventing it.
Comment 1 GitLab Migration User 2019-12-09 11:22:27 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/167.

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.