- From: Han Leon via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Jun 2019 06:46:25 +0000
- To: public-web-nfc@w3.org
> read() vs. onreading seems like not too big a difference and the ergonomics of one vs. the other seem to hinge on whether a page will typically enable a reader for multiple tag reads or only one.
Do we have any knowledge of which pattern is typically expected from POV of web developers? i.e. read once at a time OR start then just wait for events. I think usability is the most important/basic thing for decision.
If we go with the 'read once a time' pattern, we can just put the serial number back into NDEFMessage? And for any additional tag specific data regions, if they do not necessarily need to be tied with NDEFMessage, we can introduce new methods on NFCReader for getting them?
If we go with the reading event pattern, I'd like to +1 to Reilly's proposal above of changing NDEF{Message, Record} to interface type.
--
GitHub Notification of comment by leonhsl
Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/232#issuecomment-506215426 using your GitHub account
Received on Thursday, 27 June 2019 06:46:26 UTC