13 Mar
2011
13 Mar
'11
7:23 p.m.
On 03/13/11 19:44, Bernard Aboba wrote:
I agree with this in general.
However, I'd suggest that the API needs to provide more information on browser capabilities than just the supported codecs, if the goal is to permit detailed negotiations such as Jingle or SDP offer/answer. What capabilities are you thinking of?
The obvious one I think about is that the negotiation/setup needs to contain info about supportable resolutions - on a 240x400 phone screen, I have no reason to ask for 1024x768.