Re: [whatwg] AppCache Error events
Sounds reasonable to me. Webkit and chromium expose information like this via the inspector console so users/developers at that can better diagnose problems locally. Makes sense to also expose that info to app logic so developers could diagnose from afar. On Thu, Nov 29, 2012 at 11:40 AM, David Barrett-Kahn wrote: > So are there no objections to this, should I draft a change to the spec? > > -Dave > > On Mon, Nov 26, 2012 at 12:00 PM, David Barrett-Kahn > wrote: > > > Right now this event contains no structured information, just an error > > message. It'd be helpful to us to know more about what failed, so we can > > know what to report to the server and take action on. It's hard to > > distinguish cache update failures due to just being offline from those > > which are actually causing trouble. In the second case it's also hard to > > work out which resource is proving unavailable and why. > > > > One way to do this would be to create an AppCacheError subclass, with an > > errorCode parameter, and also nullable url and httpResponseCode > properties. > > Potential error codes: > > * couldn't fetch manifest (includes url and httpResponseCode) > > * pre and post update manifest fetches mismatched (includes url) > > * fetching a resource failed (includes url and httpResponseCode) > > > > Related bug: > > https://code.google.com/p/chromium/issues/detail?id=161753 > > > > Thoughts? > > > > -Dave > > > > > > > -- > -Dave >
Re: [whatwg] AppCache Error events
On Thu, 29 Nov 2012, David Barrett-Kahn wrote: > > So are there no objections to this, should I draft a change to the spec? The "process", insofar as we have one, is what is described here: http://wiki.whatwg.org/wiki/FAQ#Is_there_a_process_for_adding_new_features_to_a_specification.3F At some point, I get around to examining all the e-mails on a topic, and I try to determine what level of interest there is from implementors, and then I respond. Right now my lag is about four months, though it tends to be longer for requests for new features and shorter for major bug fixes. -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] AppCache Error events
So are there no objections to this, should I draft a change to the spec? -Dave On Mon, Nov 26, 2012 at 12:00 PM, David Barrett-Kahn wrote: > Right now this event contains no structured information, just an error > message. It'd be helpful to us to know more about what failed, so we can > know what to report to the server and take action on. It's hard to > distinguish cache update failures due to just being offline from those > which are actually causing trouble. In the second case it's also hard to > work out which resource is proving unavailable and why. > > One way to do this would be to create an AppCacheError subclass, with an > errorCode parameter, and also nullable url and httpResponseCode properties. > Potential error codes: > * couldn't fetch manifest (includes url and httpResponseCode) > * pre and post update manifest fetches mismatched (includes url) > * fetching a resource failed (includes url and httpResponseCode) > > Related bug: > https://code.google.com/p/chromium/issues/detail?id=161753 > > Thoughts? > > -Dave > > -- -Dave
[whatwg] AppCache Error events
Right now this event contains no structured information, just an error message. It'd be helpful to us to know more about what failed, so we can know what to report to the server and take action on. It's hard to distinguish cache update failures due to just being offline from those which are actually causing trouble. In the second case it's also hard to work out which resource is proving unavailable and why. One way to do this would be to create an AppCacheError subclass, with an errorCode parameter, and also nullable url and httpResponseCode properties. Potential error codes: * couldn't fetch manifest (includes url and httpResponseCode) * pre and post update manifest fetches mismatched (includes url) * fetching a resource failed (includes url and httpResponseCode) Related bug: https://code.google.com/p/chromium/issues/detail?id=161753 Thoughts? -Dave
