- From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Oct 2015 09:10:15 +0000
- To: public-web-nfc@w3.org
In the F2F, I proposed moving the contents of the [`NFCAdapter`](http://w3c.github.io/web-nfc/index.html#the-nfcadapter-interface) interface onto `navigator.nfc`, and treating them as operating on a "merged" system adapter. That is, `navigator.nfc.watch()` would watch for the next peer/tag near any of the system's adapters, and resolve the promise with that peer/tag's data. `navigator.nfc.pushMessage()` would publish the data on all of the system's adapters, and resolve or reject based on the first adapter to see a nearby peer/tag (at which point it would cancel the publication on the other adapters). The user might simultaneously tap multiple devices on the system's multiple adapters and get multiple writes, but they kinda asked for that outcome. If we eventually find a need for the developer to distinguish between multiple adapters, we can add that notion into the API then, but leaving it out could make the initial API simpler. -- GitHub Notif of comment by jyasskin See https://github.com/w3c/web-nfc/issues/67#issuecomment-151068401
Received on Monday, 26 October 2015 09:10:18 UTC