W3C home > Mailing lists > Public > public-secondscreen@w3.org > October 2015

Re: [presentation-api] PresentationReceiver: rename getConnection() and getConnections()

From: Mounir Lamouri via GitHub <sysbot+gh@w3.org>
Date: Tue, 06 Oct 2015 20:58:31 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-145998849-1444165110-sysbot+gh@w3.org>
I think the best think the spec could say is that the code above has 
an undefined behaviour. Maybe the connection will be set, maybe not. 
The code is clearly wrong, assuming that ```connections``` has one 
element which might not be the case obviously. What should be done is 
to try to use the current connections and listen for new ones, don't 
you think?

Regarding synchronous-ity, my understanding is that the main process 
will notify the child process that a connection was created. Having a 
synchronous array with an event should make the design implementatable
 in that case. I'm not sure what situation would make the synchronous 
array not implementation.

GitHub Notif of comment by mounirlamouri
Received on Tuesday, 6 October 2015 20:58:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 October 2015 20:58:33 UTC