[Bug 26776] Diagnosing and resolving CDM errors needs a numeric systemCode (deleted with MediaKeyError)

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26776

--- Comment #13 from Mark Watson <watsonm@netflix.com> ---
(In reply to David Dorwin from comment #12)
> (In reply to Mark Watson from comment #11)
> > (In reply to David Dorwin from comment #10)
> > > As discussed at TPAC, there are two issues:
> > > 1) Should we expose key-system specific values in a way that applications
> > > could switch on? (And how can we prevent/discourage that?)
> > 
> > No, client applications should not switch on key-system specific values -
> > they should be for reporting to the server for offline error analysis only.
> 
> If this is really just for offline error analysis, maybe it should be
> exposed similar to performance metrics and other things we do not expect to
> affect the behavior of the application.
> > 
> > Not sure what we can do except say that applications should not switch on
> > these, they might change etc.
> 
> If we report "metrics" rather than reporting the codes with specific events,
> it would be difficult, hacky, imprecise, and/or inadvisable to base
> application logic on it without affecting aggregate data collection.

This is all true, but I think in practice we want to know both the error code
and exactly what we were doing at the time. Also it would be important to be
able to clearly associate the error with a session for the case of debugging
individual customer problems (when looking at logs from an individual customer
or if the customer is online with Customer Services).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Saturday, 13 December 2014 00:42:17 UTC