12838 2011-05-31 23:13:51 +0000 Define garbage collection policy 2011-08-18 11:42:21 +0000 1 1 1 Unclassified WebAppsWG XHR unspecified PC All RESOLVED FIXED P2 normal --- 1 zcorpan annevk ian mike public-webapps public-webapps-bugzilla oldest_to_newest 48984 0 zcorpan 2011-05-31 23:13:51 +0000 XHR should say that an XHR object is not to be garbage collected if it can still get events and has listeners for those events. Compare with WebSocket API. 55291 1 zcorpan 2011-08-17 11:33:41 +0000 I think something along the following: UNSENT, OPENED with send() flag false can be GC (no need to mention in the spec) OPENED with send() flag true must not be GC if there are any listeners for readystatechange, loadstart, progress, abort, error, load, timeout, loadend HEADERS_RECEIVED must not be GC if there are any listeners for readystatechange, progress, abort, error, load, timeout, loadend LOADING must not be GC if there are any listeners for readystatechange, progress, abort, error, load, timeout, loadend DONE can be GC (no need to mention in the spec) If an XHR object is GC when it is in OPENED with send() flag true, HEADERS_RECEIVED, or LOADING, then the UA must act as if the user aborted the request. 55292 2 zcorpan 2011-08-17 12:12:35 +0000 websocket has: "A WebSocket object with an established connection that has data queued to be transmitted to the network must not be garbage collected." Possible that XHR should say something similar. 55304 3 annevk 2011-08-17 15:14:28 +0000 EventSource has a much simpler garbage collection policy. Would be interesting to know why that is not sufficient here. 55414 4 annevk 2011-08-18 11:42:21 +0000 Done: http://dev.w3.org/2006/webapi/XMLHttpRequest-2/#garbage-collection