- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 Oct 2015 11:19:23 +0000
- To: public-web-nfc@w3.org
We can also have a 4th option: forget the user dialog, and just have a policy with a priority list. Select the internal adapter, unless there is an external, and in case there are more, select the last which was plugged in. The essence here is to always have one adapter active with Web NFC, and to know which, by policy in this case. The concurrent use of adapters has the problems described above. I wonder how should we write the steps vs error handling. If you are adamant on this is what you want, try writing the push algorithm with this in mind and I will be happy to review it. I can also give it a try. Watches and push buffers can be made independent from the adapter, reflecting developer choice. It ultimately boils down to whether is having a user selection dialog a problem, and whether we explicitly want concurrent handling of multiple adapters. -- GitHub Notif of comment by zolkis See https://github.com/w3c/web-nfc/issues/67#issuecomment-151459487
Received on Tuesday, 27 October 2015 11:19:26 UTC