Opened 7 years ago

Closed 6 years ago

Last modified 6 years ago

#15194 closed enhancement (fixed)

decide and implement loader error recovery strategy

Reported by: Rawld Gill Owned by: Rawld Gill
Priority: low Milestone: 1.7
Component: Loader Version: 1.7.2
Keywords: Cc: cjolif
Blocked By: Blocking:

Description

Currently, the AMD spec only requires an error be signaled. There is no requirement for the ability to recover. In fact, in most cases, recovery is impossible and the application is simply doomed. However, in some cases it may be desirable to allow for recovery (for example, where a known alternative source of a module is available or networks where a retry might have different results) .

The current amd-thread for error recovery is here: http://groups.google.com/group/amd-implement/browse_thread/thread/bb47f5eb576b7490

Change History (5)

comment:1 Changed 7 years ago by Rawld Gill

Milestone: tbdfuture
Priority: undecidedlow
Status: newassigned

comment:2 Changed 7 years ago by cjolif

Cc: cjolif added

comment:3 Changed 7 years ago by Rawld Gill

See also #13825 and #14862

comment:4 Changed 6 years ago by Rawld Gill

Resolution: fixed
Status: assignedclosed

#16416 includes a demo of how to recover when a module fails to load. No more is planned until AMD has a spec in this.

comment:5 Changed 6 years ago by bill

Milestone: future1.7

Can't close something as fixed with milestone "future". I guess you mean to use require.on("error", ... in which case that was presumably supported since 1.7.

Note: See TracTickets for help on using tickets.