- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Thu, 10 May 2012 11:50:33 -0700
- To: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
- Cc: Cullen Jennings <fluffy@cisco.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>, Justin Uberti <juberti@google.com>, Adam Bergkvist <adam.bergkvist@ericsson.com>
On 9 May 2012 23:47, Ravindran, Parthasarathi <pravindran@sonusnet.com> wrote:
> Async proposal looks more appropriate as createOffer is equivalent to get
> capability of the browser and setLocalDescription is based on the policy of
> the WebRTC application. Based on my Customer Premises Equipment development
> understanding, it takes time to load the specific codec into DSP based
> devices and not possible to load all the codec at the same time.
That's an argument for setLocalDescription being async. It's still
likely a good argument for createOffer/createAnswer being async too,
but you wont be actually loading codecs in response to createOffer.
Of course, everything should be async so that we have to write code like:
a(function(b) {
b.c(function(d) {
d.e(function(f) {
// etc...
}}}
Received on Thursday, 10 May 2012 18:51:03 UTC