Re: telepathy roadmap and media streaming

I think abstracting stuff into seperate concepts of a video call and a
voice call would be unwise, because at least in Jingle calls, individual
streams can come and go during the lifetime of a call. Ie, you can be in
a voice call and plug in a webcam and then offer a video stream to
somebody. They could then go "oh yes what a good idea", and then plug
their webcam in, and upgrade the video stream to bidirectional...
There's a reason that the Telepathy API exposes the streams to you, each
with their own directionality. :)

Regards,
Rob

Jimen Ching wrote:
> Hi all,
> 
> Since development is continuing on the telepathy branch, I was curious as
> to what the criteria is for merging this branch into HEAD.  Does the
> branch have to be as far along in terms of Jabber support before it can be
> merged?
> 
> On a similar note; has anyone thought about how to support media
> streaming (voice/video chat)?  Since telepathy is now treated just like a
> protocol, I assume this means the media streaming architecture needs to be
> as flexible as the account management.  I assume the API could be as
> simple as:
> 
> 	request_voice_chat
> 	cancel_voice_chat
> 	accept_voice_chat
> 	reject_voice_chat
> 
> The Telepathy spec supports uni- and bi-directional media streaming.  I'm
> not sure how to present an interface to the user for this feature.
> There's also the issue with talking with multiple contacts.  I'm thinking
> of call-waiting...
> 
> As for video, I assume something similar would work:
> 
> 	request_video_chat
> 	cancel_video_chat
> 	publish_video_chat
> 	accept_video_chat
> 	reject_video_chat
> 
> I don't know whether all IM protocols support video chats in this fashion.
> 
> Comments anyone?
> 
> --jc


-- 
Robert McQueen
Director, Collabora Ltd.