Dan Mosedale wrote:
> I suspect that nsIErrorService will probably be the most straightforward way
> to propagate network-level errors up to the UI, since it's designed
> for just this purpose. nsIException support just landed recently
> <http://lxr.mozilla.org/seamonkey/source/xpcom/base/nsIException.idl>,
> so it would also be interesting to hear whether the netlib folks have
> any plans to move in that direction, and what the stated XPCOM
> direction is...
I believe that the nsIException and related interfaces will be used to
propogate rich exception details across xpcom boundaries. nsIException
allows for custom exception messages, and even a facility for extracting
a stack trace.
I believe that the DOM will use nsIException to report errors to the
caller, and eventually all xpcom languages will use nsIException so rich
errors can cross xpcom boundaries.
I believe that if I say "I believe" any more someone will hit me :)
However, I don't want to speak for anyone else :)
See http://bugzilla.mozilla.org/show_bug.cgi?id=65080
Mark.
