- From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
- Date: Thu, 29 Oct 2015 11:12:06 +0000
- To: public-web-nfc@w3.org
In [case 2](https://github.com/w3c/web-nfc/issues/67#issuecomment-151847008), I'd probably have the UA take the following steps, if the underlying APIs make it possible. 1. Publish the message to all adapters. 2. When one adapter discovers a tag/peer and starts writing to it, attempt to unpublish the message from all other adapters. 3. If any of the other adapters has already started writing by the time the unpublish request arrives, allow it to continue. 4. Wait until all of the active writes attempts succeed or fail. 5. If any succeeded, fulfil the promise. Otherwise, reject it. I'm suggesting to fulfil if any succeed because that tells the developer whether the state of the external world changed. -- GitHub Notif of comment by jyasskin See https://github.com/w3c/web-nfc/issues/67#issuecomment-152148938
Received on Thursday, 29 October 2015 11:12:08 UTC