[web-nfc] Should there be two pushMessage methods or not

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

== Should there be two pushMessage methods or not ==
https://github.com/w3ctag/spec-reviews/blob/master/2015/10/nfc-feedback.md

> pushMessage can only have two active pushes happening at once--one 
for tags, the other for peers. Is this a list expected to expand? If 
this is a fixed set of things, then could the API be simplifid by 
having separate pushToTag() and pushToPeer() APIs? (Not sure if this 
would be a good thing.)

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

Received on Thursday, 15 October 2015 09:26:04 UTC