Exactly Ben, except when PHP fails, even with a Fatal Error, the page has status 200, we need to understand which call failed between hundreds of potential calls in the debugger, and errors could pass silently. With Formaldehyde, accordingly with your predefined error_reporting level, above situation will never happen, and the entire process, without changing anything, will be much simpler, as Ben already described. So yes Tedd, you did not even read what is Formaldehyde about ... please try to understand it before other comments, maybe you'll discover it's extremely simple, and hopefully useful. Regards > Date: Fri, 11 Sep 2009 10:43:23 -0700 > Subject: Re: RE: [Formaldehyde] The Most Basic Ajax - PHP Error Debugger > From: bdunlap@xxxxxxxxxxxxxxxxxx > To: tedd.sperling@xxxxxxxxx > CC: an_red@xxxxxxxxxxx; php-general@xxxxxxxxxxxxx > > > Examine this: > > > > http://webbytedd.com/a/ajax-site/js/a.js > > > > Now, where can something go wrong? > > I suppose slave.php could fail with a 4xx or 5xx response. Then, most > likely, the user would be left clicking on a link that does nothing. > In an edge case the body of the error-response might include a '|' > character, which would really mix things up. > > Certainly, you wouldn't /need/ Formaldehyde to debug this, but it > might make the process a bit simpler -- if I read the docs correctly, > Formaldehyde would let you see and grasp the whole problem instantly > from a browser, without having to resort to web-server logs, etc. > > Ben _________________________________________________________________ Show them the way! Add maps and directions to your party invites. http://www.microsoft.com/windows/windowslive/products/events.aspx
