- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 Nov 2019 16:57:14 +0000
- To: public-web-nfc@w3.org
> I believe web developers would naively assume something like this shoud work. That should indeed work and fulfills the use case in my view as well. However, I didn't fully understand whether does Kenneth want to tell the implementation to make optimizations for updating if possible (instead of separate read/write cycle), or whether he just wanted a syntactic sugar for the whole read/write cycle. At least in Android, I don't think a full vertical read/write buffer optimization is possible, and at SNEP level certainly there is no optimization. So I think it's probably the syntactic sugar. Even then, it might add complexity/confusion to the API. I like the current simple way. Maybe we need more examples/experience with this use case. -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/315#issuecomment-549447725 using your GitHub account
Received on Monday, 4 November 2019 16:57:15 UTC