- From: Louay Bassbouss via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Apr 2015 14:26:29 +0000
- To: public-secondscreen@w3.org
@anssiko comment on this: >That is a good question. Whatever we decide, we should specify the expected behaviour in order to allow the implementations to interoperate after we've figured out whether the API should work with data URIs. > I think there may be a disagreement among implementers whether data URIs are same-origin depending on where they're used (Worker, iframe, img, open()...). I think the closest existing API to startSession() where data URIs can be used is open(). > I think the primary motivation for using data URIs has been performance. HTTP/1.x has known limitations in loading multiple resources concurrently, so inlining all the resources has improved the performance. Another use case I can think of is to be able to provide a single file that contains all the resources without the need to package multiple files together. > Louay, All - I think you should investigate this further and come up with a recommendation on how to proceed i.e. whether data URIs should be allowed or not, and how to spec that -- GitHub Notif of comment by louaybassbouss See https://github.com/w3c/presentation-api/issues/76#issuecomment-91574683
Received on Friday, 10 April 2015 14:26:40 UTC