[web-nfc] cancelPush() should have target ?

riju has just created a new issue for https://github.com/w3c/web-nfc:

== cancelPush() should have target ? ==
At any moment, there can be a maximum of 2 pushMessage() for an 
adapter, 1 for tag, 1 for peer.
So correspondingly 2 messageBuffer/NFCMessage, 2 timers, etc. 
Presently in cancelPush(), all the instances of pushMessage() are 
invalidated. 
Do you want to add "target" as a parameter to cancelPush() ?


See https://github.com/w3c/web-nfc/issues/54

Received on Wednesday, 23 September 2015 08:58:05 UTC