- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Fri, 30 Aug 2019 11:11:31 +0000
- To: public-web-nfc@w3.org
SNEP will overwrite records on the target anyway. I don't get what we want to achieve here. What is the use case? Read a tag and reuse those records for pushing (after modifying them)? The underlying implementation will likely have to create a new SNEP message anyway, regardless how it's exposed in native or web APIs. But if you want to "save" memory on bindings side that's possible, so I assume you are saying the API should be able to provide hints to the implementation that "in fact I want to do an update to a target"? -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/315#issuecomment-526562232 using your GitHub account
Received on Friday, 30 August 2019 11:11:32 UTC