- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Thu, 29 Oct 2015 06:35:51 +0000
- To: public-web-nfc@w3.org
Yeah, transactions and rollback look like overkill, considering the very small likelyhood we run into this corner case: they are not worth implementing. Then, Jeffrey's suggestion of handling adapters in parallel has more appeal than selecting a single adapter and deal with multiplicity by applying a policy (or selection dialog), and definitely better than not dealing with multiplicity at all. I think that was a nice cut through, kudos. I just have a problem with writing the push steps for it. Since I cannot imagine a use case which would _require_ simultaneous tapping of multiple tags, could we say in the spec that multiple adapters are supported as long as only one of them is used by the user at any given time, and concurrent use will likely work with reads, but may result in push errors in some of the adapters which means partial success? And in the case of an error, we reject, and the user should try again? Then we could take option 3, as it got most votes so far. -- GitHub Notif of comment by zolkis See https://github.com/w3c/web-nfc/issues/67#issuecomment-152095756
Received on Thursday, 29 October 2015 06:35:54 UTC