Integrating the Webs' dependency systems
zenparsing at gmail.com
Tue May 27 15:36:47 PDT 2014
> I don't think a URL is the right way to identify everything. Many things
> in the Web platform that you could legitimately want to depend on don't
> have a URL. For example, a promise, or an inline <script> block, or an
> HTML <video> element (the latter in particular would have several URLs,
> the whole point would be to depend on the element so that things only
> happen once that element has figured out which file it wants to play and
> is ready to do so).
How would you identify such dependencies, within this system? (The
identification must somehow allow de-duplication.)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss