- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Thu, 21 Jun 2012 13:46:21 -0700
- To: Harald Alvestrand <harald@alvestrand.no>
- Cc: Li Li <Li.NJ.Li@huawei.com>, Justin Uberti <juberti@google.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
If you can only handle two specific configurations, then being prepared to ask for a stream multiple times with very specific mandatory constraints and using a try, fail, fallback approach sounds appropriate. It's not like this is going to take very long. On 21 June 2012 13:28, Harald Alvestrand <harald@alvestrand.no> wrote: > But generality is very costly. That can go both ways: generality in the API can save the need for generality in the application. As in this case, even if I'm not sure it is sufficiently motivated, more generality could have made the application task easier.
Received on Thursday, 21 June 2012 20:46:51 UTC