- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Apr 2017 16:50:56 +0000
- To: public-secondscreen@w3.org
I could see two options to address this: 1. Allow implementations to cap the size of the PresesntationConnectionList. This does not require a normative spec change. Very long running presentations (perhaps accessible through a public kiosk) would run the risk of hitting this limit by filling up with closed connections, and then failing to accept new connections. They could reload themselves periodically to empty the list. 2. Propose and land the spec change to remove closed connections from the set of presentation controllers, which is future proof, but would possibly be another feature at risk in PR given the time frame and implementation resources available. Landing a spec change in "level 2" to address this could be difficult, since I am not sure how to easily detect content that is dependent on having closed connections in the list, and thus assess the web compatibility risk. I am leaning towards 2, generally future proofing is better, but welcome input from @schien on this. -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/419#issuecomment-294189530 using your GitHub account
Received on Friday, 14 April 2017 16:51:05 UTC