xhr try/catch handler

[prashantjain68]

I am new to dojo and learning dojo the hard way which is debugging the source code.

One thing I noticed: All my errors originated from the xhr class (as per the Chrome console). In one case, my xhr call succeeded but still the error handler registered with xhr was called. After debugging, I realized that my callback was being invoked in a try/ catch block in the xhr class, line 432. The callback then executed another 5000 lines of code and if there is an error in one of them, the xhr calls the error handler or reports to the browser that an error occurred in xhr line 432. I am now putting break points at different places in those 5000 lines of code to see where the error is actually happening.

This is very mis-leading and a nightmare to debug. The load and error callback registered with xhr should not be called within a try/ catch.

[prashantjain68]

Browser error and callstack

[dylan]

Given that dojo/_base/xhr has been deprecated in favor of dojo/request, I'm going to close this out.