<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 03/13/11 19:44, Bernard Aboba wrote:
<blockquote cite="mid:BLU152-w601174B59055DB7F3124D693CD0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
I agree with this in general. <br>
<br>
However, I'd suggest that the API needs to provide more
information on browser capabilities than just the supported<br>
codecs, if the goal is to permit detailed negotiations such as
Jingle or SDP offer/answer. <br>
</blockquote>
What capabilities are you thinking of?<br>
<br>
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.<br>
<br>
</body>
</html>