- From: Mark R. James via GitHub <sysbot+gh@w3.org>
- Date: Sun, 06 Sep 2015 22:31:49 +0000
- To: public-web-nfc@w3.org
If new messages update pending ones, then given the max. 10s timeout, there's less need for a cancel. There is though a bit of a security worry that there's up to a 10s window when data could be sent to an unauthorised party if the user is distracted after initiating a send, with no way to cancel. I agree that the semantics of pushing an updated message during the data transfer period is less important. Queuing or rejection may be the best choice, because a delayed pushMessage return would be unexpected for an asynchronous command, and may lock-up the UI. -- GitHub Notif of comment by mrj See https://github.com/w3c/web-nfc/issues/45#issuecomment-138133320
Received on Sunday, 6 September 2015 22:31:51 UTC