On Jul 7, 12:42 pm, Walter Lee Davis <wa...@wdstudio.com> wrote: > I've used 409 (Conflict) a lot to signal back to my application that > an Ajax request went wrong at the server level (409 and Ajax are both > powerful household cleaner brands, so it's my private-joke-over-HTTP > status). But if I want to be semantic at the error code level, what > code best signals "you, the user, did something incomplete or wrong, > so you are not getting a 200 for your effort"? > > Thanks, > > Walter
To my mind, HTTP response codes aren't for application logic signalling. They're for signalling between the browser and server. The correct response to bum data from the user is a 200 with an application-logic-level success/error flag. I wouldn't conflate the transport and business logic layer errors. (The 409 / Ajax thing *is* funny.) FWIW... -- T.J. Crowder Independent Software Engineer tj / crowder software / com www / crowder software / com -- You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptaculous@googlegroups.com. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
