| Summary: | Add Call1.Stream.InitialDirection property | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Guillaume Desmottes <guillaume.desmottes> |
| Component: | tp-spec | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | enhancement | ||
| Priority: | medium | CC: | olivier.crete |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | call-later | ||
| i915 platform: | i915 features: | ||
|
Description
Guillaume Desmottes
2012-02-20 01:11:23 UTC
InitialDirection on the channel? or on the Content? Also, for the initial audio/video contents, it's not required as the Handler can just do SetSending(False) or RequestReceiving(False) on the streams before calling Accept() on the Call channel. (In reply to comment #1) > InitialDirection on the channel? or on the Content? If you want it to be settable during the channel request (like InitialAudio), it'd have to be on the Channel. As a requestable property? Then would be want a InitialAudioDirection/InitialVideoDirection ? I think having them as requestable properties is pointless. -- 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/129. |
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.