I never meant to imply that onComplete did the same thing as onSuccess, what
I meant to state was that onComplete ALWAYS gets called last. onSuccess can
always set a flag and onComplete can do the UI updates right before turning
off the spinner. This is useful if you're experiencing those
"asynchronicity" problems that the OP thought he had... Almost a poor mans
On Fri, Sep 30, 2011 at 7:53 AM, Chris Sansom <ch...@highway57.co.uk> wrote:
> On 30 Sep 2011, at 12:32, Richard Quadling wrote:
> > onFailure / onSuccess is in response to a working result from the AJAX
> > onComplete is in response to the AJAX mechanism shutting down.
> > onComplete will always be called, but it isn't its job to deal with
> > the data from the call. That is onSuccess. If the call failed for some
> > reason, onComplete wouldn't have any data to work with and could make
> > things worse.
> > I use onCreate and onComplete to turn on/off a little spinner showing
> > that the app is doing something behind the scenes.
> Right - thanks. That could be useful.
> Cheers... Chris
> Highway 57 Web Development -- <http://www.highway57.co.uk/>
> 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
> To unsubscribe from this group, send email to
> For more options, visit this group at
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 email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at