- From: Anton Vayvod via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Dec 2015 13:51:39 +0000
- To: public-secondscreen@w3.org
Since sending and receiving messages to/from a "connecting" connection might sound confusing, and w/o this extra functionality "connecting" state doesn't add much, maybe there're other ways we could workaround passing the metadata etc? 1. Return the PresentationConnection in a "disconnected" state when the user picks a screen, but with some custom dictionary "screen" field that would contain the available metadata? Once the connection is established, the PresentationConnection changes to a "connected" state. 2. Return the PresentationConnection in a "connected" state when the user picks a screen to allow messaging and handle the messages requiring a working connection by queueing them until the underlying connection to the screen is established. -- GitHub Notification of comment by avayvod Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/214#issuecomment-165111350 using your GitHub account
Received on Wednesday, 16 December 2015 13:51:40 UTC