#6301 NORM Never A: handle incoming media channels as video call activity invites

[Zarro Boogs per Child]

#6301: handle incoming media channels as video call activity invites
----------------------------------+-----------------------------------------
  Reporter:  robot101             |       Owner:  Collabora     
      Type:  enhancement          |      Status:  new           
  Priority:  normal               |   Milestone:  Never Assigned
 Component:  video-chat-activity  |     Version:                
Resolution:                       |    Keywords:                
  Verified:  0                    |    Blocking:                
 Blockedby:                       |  
----------------------------------+-----------------------------------------

Comment(by bemasc):

 I am an Activity developer.  I want to push some arbitrary real-time data
 across the network for my shared session, so I ask Telepathy for a RTP
 channel.  It may be that my data is in fact Speex-encoded voice, or
 thermometer readings, or something else.  The purpose of the channel is
 unknown to Telepathy; conversely, the backend being used by Telepathy is
 unknown to the Activity.

 This design does not require or utilize any XMPP capabilities.

 Replying to [comment:6 daf]:
 > Even in the two-person case, Gabble can't call someone without seeing a
 capability advertisement from them

 Gabble doesn't call people.  People are invited to a shared instance of
 the Call activity.

 To step back for a moment, the purpose of capability standards is to allow
 multiple compatible implementations of a capability to recognize each
 other.  This is irrelevant in the case of Sugar, because Activity A only
 ever communicates with other instances of Activity A.  There is no
 possibility of communication between different clients, so there is no
 need for generic capabilities.

-- 
Ticket URL: <http://dev.laptop.org/ticket/6301#comment:7>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system