- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Oct 2015 11:55:12 +0000
- To: public-web-nfc@w3.org
We should avoid enumeration... Supporting multiplicity does not change the API with the pattern above. As for the example, we have 2 different adapters that can work in parallel. 1. we should not release nfcAdapter, unless the underlying platform can only work with one. 2. we don't reject promise for first push 3. we don't move watch/push to the new adapter 4. developer has chosen to write this code. It is legal, but not wise. Instead of id, they get an object. If they lose the object, it will leak until the page is closed/reloaded. 5. I think we could have internal + USB adapter. However: if we decide to not support multiple adapters, no need to change the API. Even in that case, it should be noted in the spec that an NFC adapter is a singleton per physical adapter+script execution context. -- GitHub Notif of comment by zolkis See https://github.com/w3c/web-nfc/issues/67#issuecomment-150552581
Received on Friday, 23 October 2015 11:55:15 UTC