- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Aug 2017 03:49:16 +0000
- To: public-webscreens@w3.org
This looks very good and well documented! One thing that we already discussed in the past (although I'm not clear we came to a conclusion) is that, if I understand correctly, the suggested "Presentation Display Availability Request" will leak presentation request URLs to discovered receivers at a stage where the user has not yet given her consent to use any specific receiver, that is before the user selects the receiver. Now this approach has the advantage of allowing any kind of suport logic in receivers. Any alternative would be much less flexible, as it would require a declarative mechanism that receivers would use to explain what types of URLs they support, and which the controller would in turn use to decide whether a given receiver is likely compatible with a given URL. PS: FWIW, there are a few typos here and there. I'll try to point them out when I have more time available. -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/webscreens/openscreenprotocol/pull/44#issuecomment-325872099 using your GitHub account
Received on Wednesday, 30 August 2017 03:49:12 UTC