| 12:05 | <lgrahl> | FYI the WebRTC guys are considering the use of streams for media as well but there are a lot of open questions. Maybe some of you can help answering them or comment on it: https://lists.w3.org/Archives/Public/public-webrtc/2018Jun/0039.html |
| 12:06 | <lgrahl> | I don't want them to reinvent the wheel if not necessary :) |
| 14:10 | <wanderview> | JakeA: can't a targetClientId be null? |
| 14:10 | <wanderview> | or maybe I have forgotten how targetClientId is supposed to work... I've been manually focused on resultingClientId |
| 14:10 | <JakeA> | wanderview: hmm, I guess if can be if it's cross-origin |
| 14:10 | <JakeA> | it can* |
| 14:10 | <wanderview> | JakeA: or opening a brand new tab? |
| 14:10 | <JakeA> | yeah |
| 14:11 | <JakeA> | good point |
| 14:44 | <Domenic> | lgrahl: as much as I would like to see Web RTC use Streams properly, it seems like a long and expensive education campaign, much of which would be done on mailing lists I don't have easy access to. So my current strategy is to just hope for the best. Eventually they figured out promises, at some cost to them due to the transition. Probably similar things will happen for streams. |