On Wed, 16 Dec 2009, Andrei Popescu wrote:
> >> > If I understand the example correctly, the video element will show
> >> > the output of the user's camera (i.e. act as an embedded camera
> >> > viewport). To be able to implement video chat, we also need a way
> >> > to see the remote party, so we need a way to send the Stream over
> >> > to some server. I think we should specify the mechanism for doing
> >> > that (e.g. WebSockets::send(Stream stream)).
> >>
> >> I believe this is the plan yes, if the general proposal can be made
> >> to work.
> >
> > Indeed. The problem is that this requires a chosen codec, and we don't
> > have one. That's why I stopped where I did.
>
> Perhaps I am missing something, but this requirement isn't entirely
> obvious to me :) Why do we need to agree on a codec any more than we
> needed for the <video> tag?
We need to for <video> also.
However, in this case we need to even more, because otherwise there's no
guarantee that a user with one browser could chat to a user with another
browser, which makes the whole exercise pointless.
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'