[Bug 28717] New: Make sure we document nicely what the RequestableChannelCalss for Call should be

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=28717

           Summary: Make sure we document nicely what the
                    RequestableChannelCalss for Call should be
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: tp-spec
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: sjoerd at luon.net
         QAContact: telepathy-bugs at lists.freedesktop.org


>From #24936:

Some comments while working on the Call example CM:

* InitialTransport should be specified to be "" where not applicable, and in
particular, on CMs with hardware streaming

* The immutable properties on Channel, Stream and Content should all be
annotated as such

More thoughts:

Sjoerd and I agreed that the RequestableChannelClasses should be:

* fixed = { Call, CONTACT, InitialAudio=TRUE }, allowed = { InitialVideo=TRUE }
* fixed = { Call, CONTACT, InitialVideo=TRUE }, allowed = { InitialAudio=TRUE }

i.e. clients aren't allowed to make outgoing calls that have neither initial
audio nor initial video. This doesn't match StreamedMedia, and doesn't match
telepathy-qt4's current handling of StreamedMedia capabilities - it'll be
important to check at review that it gets this right.

The initial streams should have the Initial disposition, even though that's not
interesting on locally-initiated streams.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.