- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Oct 2015 09:31:14 +0000
- To: public-web-nfc@w3.org
When pushing, it is non-deterministic on which adapter the push/write happened, and the web page would not know either. Basically that is not such a big problem. If it was the wrong one, and timeout happens, the page can ask again, and again,... until the user realizes the wrong adapter was used. Which is not much different from the case when we would have had 2 adapter objects. When reading from 2 adapters far enough to not have interference/race, we don't have a problem merging them. When they are too close, it gets non-deterministic, but similarly as above, in the end the use case is handled the same way. In summary, we can try to implement this, and modify the spec accordingly. This would also have the advantage of attaching permissions to the leaves, i.e. navigator.nfc.watch() and navigator.nfc.push(). -- GitHub Notif of comment by zolkis See https://github.com/w3c/web-nfc/issues/67#issuecomment-151077258
Received on Monday, 26 October 2015 09:31:16 UTC