- From: Louay Bassbouss via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Nov 2015 07:18:44 +0000
- To: public-secondscreen@w3.org
@karim76 thx for your feedback I agree with you about your concern if devices are not in the same network and but there are cases where BLE makes sense. Example: Present on a Display as guest (Controller and display are not in the same network but both are connected to the internet). In this case BLE will help to discover the display and maybe exchange some signalling information and launch the presentation. for communication WebRTC can be used. This should be possible even if the devices are not in the same network. BLE can be used as signalling channel e.g. to exchange WebRTC metadata (offer, answer, etc.). It is also possible to use WebSocket for the communication instead of WebRTC but this must be routed over a cloud server. In this case, during the BLE discovery the display sends its remote Endpoint and the controller connects to it. To makes things clear: my proposal was only to put BLE in the discussion but not necessary as main protocol for discovery. maybe as additional optional protocol if we see there are relevant use cases for it. most currently available presentation devices (mainly TVs and streaming devices) support IP based discovery protocols (mDNS/DNS-SD, SSDP) and we should consider them first. -- GitHub Notif of comment by louaybassbouss See https://github.com/w3c/presentation-api/issues/220#issuecomment-156021352
Received on Thursday, 12 November 2015 07:18:47 UTC