I can recall desk phones from the past where hardware support provided for things like encoding/decoding and encryption/decryption, and the number of parallel streams or stream combinations was limited. Whether this is still true for today's/tomorrow's hardware I am not so sure. But even if there is a restriction on the number of streams or stream combinations, we also have to consider that different applications might be using the browser (or different instances of the browser, or even different browsers), and these different applications could each place their own demands on hardware/software resources. For example, one application could be doing video streaming, and another application could be doing real-time voice or voice/video. The different applications will certainly be unaware of each other, so any assumption by an application that a given combination of streams is possible, based on its browser's static capabilities, might not be true if that combination is actually requested. In this circumstance the browser would either have to deny the request, or accept it and grant a "best effort" use of shared resources. John
-----Original Message----- From: rtc-web-bounces@alvestrand.no [mailto:rtc-web-bounces@alvestrand.no] On Behalf Of Markus.Isomaki@nokia.com Sent: 15 March 2011 08:45 To: harald@alvestrand.no; christer.holmberg@ericsson.com Cc: bernard_aboba@hotmail.com; rtc-web@alvestrand.no; jonathan.rosenberg@skype.net Subject: Re: [RTW] Review of draft-holmberg-rtcweb-ucreqs-00 (Web Real-Time Communication Use-cases and Requirements)
Harald Alvestrand wrote:
Do you know of ONE device, presently existing in the Real World (that is, outside of labs) that supports TWO specific, different
codecs, and
is able to use either of them, but is not able to use them at the same time?
I can confirm that there are currently mobile phones on the market, that do have this type of restrictions, i.e. they in general support certain audio and certain video codecs with certain modes, but not all combinations of them, due to limited HW. And these are phones that do have SIP VoIP/video clients, so in that sense they are relevant. So if we want to take RTC-Web to as low end as SIP has already gone, the issue is probably real. At the moment these devices don't typically have a browser with all bells and whistles, though.
Markus _______________________________________________ RTC-Web mailing list RTC-Web@alvestrand.no http://www.alvestrand.no/mailman/listinfo/rtc-web