On Jul 7, 1:27 pm, Walter Lee Davis <wa...@wdstudio.com> wrote:
> On Jul 7, 2011, at 8:21 AM, T.J. Crowder wrote:
> > 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.
> Fair enough, but since the onFailure callback only runs if the
> response code sent back is something other than the 200 range, how
> would you recommend I send back that failure other than with the
> status code?
Let's just say I never use Ajax.Request directly. :-) I put in
application-level plumbing and take care of things like providing a
`context` parameter for callbacks and handling both transport and
application logic errors.
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 firstname.lastname@example.org.
To unsubscribe from this group, send email to
For more options, visit this group at