Comments on: Losing REST over Ajax Errors? http://www.sitepoint.com/blogs/2007/04/04/losing-rest-over-ajax-errors/ News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com. Fri, 05 Dec 2008 00:18:05 +0000 http://wordpress.org/?v=2.5 By: Bryan Rasmussen http://www.sitepoint.com/blogs/2007/04/04/losing-rest-over-ajax-errors/#comment-219823 Bryan Rasmussen Sat, 07 Apr 2007 09:41:50 +0000 http://www.sitepoint.com/blogs/2007/04/04/losing-rest-over-ajax-errors/#comment-219823 I think I would use arrays for this, one for response codes, one for responses, if index out of range throw error, if response code not supported ignore response, choice as to whether to retry in bit or stop processing. I think I would use arrays for this, one for response codes, one for responses, if index out of range throw error, if response code not supported ignore response, choice as to whether to retry in bit or stop processing.

]]> By: plumsauce http://www.sitepoint.com/blogs/2007/04/04/losing-rest-over-ajax-errors/#comment-217896 plumsauce Wed, 04 Apr 2007 07:05:30 +0000 http://www.sitepoint.com/blogs/2007/04/04/losing-rest-over-ajax-errors/#comment-217896 Since a lot of Ajax enthusiasts will land here, I'll take this opportunity to post a suggestion: Avoid xmlhttp! Not that the component does not work, but because it throws a truly ugly error if the user has error messages enabled and activex disabled. So annoying! Since a lot of Ajax enthusiasts will land here, I’ll take this opportunity to post a suggestion:

Avoid xmlhttp!

Not that the component does not work, but because it throws a truly ugly error if the user has error messages enabled and activex disabled.

So annoying!

]]> By: pauldwaite http://www.sitepoint.com/blogs/2007/04/04/losing-rest-over-ajax-errors/#comment-217895 pauldwaite Wed, 04 Apr 2007 06:55:02 +0000 http://www.sitepoint.com/blogs/2007/04/04/losing-rest-over-ajax-errors/#comment-217895 Just in case people mentally blocked the "first step" bit, HTTP != REST. Just in case people mentally blocked the “first step” bit, HTTP != REST.

]]> By: cranial-bore http://www.sitepoint.com/blogs/2007/04/04/losing-rest-over-ajax-errors/#comment-217786 cranial-bore Wed, 04 Apr 2007 02:00:10 +0000 http://www.sitepoint.com/blogs/2007/04/04/losing-rest-over-ajax-errors/#comment-217786 Good idea. I was just thinking recently about the need for Javascript to be aware of both errors with the Ajax transactions, and errors on the server side as well. Good idea. I was just thinking recently about the need for Javascript to be aware of both errors with the Ajax transactions, and errors on the server side as well.

]]> By: tuna http://www.sitepoint.com/blogs/2007/04/04/losing-rest-over-ajax-errors/#comment-217773 tuna Wed, 04 Apr 2007 01:36:00 +0000 http://www.sitepoint.com/blogs/2007/04/04/losing-rest-over-ajax-errors/#comment-217773 humm this is real old school programming method..just proves sometimes the old ways do have merit. :) humm this is real old school programming method..just proves sometimes the old ways do have merit. :)

]]> By: chrisb http://www.sitepoint.com/blogs/2007/04/04/losing-rest-over-ajax-errors/#comment-217758 chrisb Wed, 04 Apr 2007 00:42:29 +0000 http://www.sitepoint.com/blogs/2007/04/04/losing-rest-over-ajax-errors/#comment-217758 so long as they remember what readystate 4 means.. so long as they remember what readystate 4 means..

]]>