I owe everyone a draft of the loader semantics, but for now here's a way to think about the interface between Ecma-262 and the loader spec: the "names" the ES spec is talking about are *not* the names used by the loader or in the registry. They are just GUIDs -- you can think of them as just being references to the internal module record, but serialized as GUID strings. AIUI Allen wanted to reify them as strings just to provide a more abstract way for the loader spec to reference module records without actually looking at their internals.
The actual loading happens -- completely asynchronously -- in the loader spec, not in ECMAScript. The HostGetSource and HostNormalizeModuleName are just retrieving an association that's assumed to be provided through other means. Hopefully this will look clearer with an asynchronous loader spec to review. Dave On Wed, Dec 10, 2014 at 4:57 AM, Guy Bedford <[email protected]> wrote: > Do the HostGetSource and HostNormalizeModuleName functions allow for > asynchronous completion, or are they expected to be synchronous? > > Specifically I'd be interested to hear if the browser loader would run its > own dependency tree handling or if it should rely on these hooks implicitly > managing the dependency tree for it. > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
