On Fri, 29 Aug 2014, David Herman wrote: > > It's still not completely clear to me what your use cases are, so I'm > not sure exactly how much user-visible API you need.
My goal is to avoid browsers having to implement two dependency systems (one for ES modules, one for HTML imports). > But if you are trying to reflect the browser's fetching policies and > priorities based on different types of assets, then you are looking for > a layer in between ServiceWorker and module loader -- call it an asset > manager or resource manager. Right. But that kind of system will have dependencies to track, including dependencies between ES6 modules, and on ES6 modules from other things, and from ES6 modules to other things. I don't understand how to make that work if we're not able to have a single dependency system. > I'd be happy to discuss this with you and see if we can flesh out the > use cases and requirements to get a better handle on the problem space. I would love that. Where and when? You may also find the following helpful in explaining things I'm looking at at the moment related to this: http://lists.w3.org/Archives/Public/public-whatwg-archive/2014Aug/0177.html -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' _______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
