I think I agree with John on this (and not because I just pre-orderd his
new book through Amazon). :o)
In the scenario of all 404 and 500 errors being mapped to 200, isn't
there a better way of handling that?
Maybe via the Custom Errors tab in IIS or the .htaccess file in apache?
I don't know, I've not had to do it before, but I was reasonably certain
it was possible. Like I said, I don't know, maybe there's a specific
reason that Dave needs to map all error codes to 200, and it may be
perfectly reasonable. Just my two cents I suppose. :o)
Chris
John Resig wrote:
That said, I think it should be as fail-safe as possible.
But which is worse - throwing an exception inside of jQuery due to
malformed JSON data - or silently dying?
I mean, as it stands right now, jQuery assumes that all data coming
into it (selectors, arguments, etc.) are well-formed. Beyond that,
it's quite a gray area.
I'm personally against having empty try/catch blocks to hide errors -
they almost always cause more confusion than what they're worth.
--John
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
