On May 17, 2007, at 1:18 AM, Christophe Porteneuve wrote: >> OnSuccess happens the moment that the Updater connects to the server >> or >> whatever it's contacting. It's that kind of success, not the success >> of >> finishing something. > > Sorry to say, but 100% wrong. > > onSuccess is a Prototype-based event that triggers alternatively to > onFailure *right before* onComplete, based on the analysis of the HTTP > response status code ([200;300[).
Okay, I see what you mean, but I have to say, not entirely 100% wrong either. Status headers are the very first thing that a Web server sends in response to a request. They are the conversational equivalent of clearing your throat before you start speaking. You may then follow that by a mighty pause before saying something extremely clever (or mistaken, if you are me). From the point of view of the receiving script, a status 200 will trigger onSuccess, but that doesn't mean that the rest of the data has come along. It just means that the request was successful. That's all I was trying to get across to the OP. Walter --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
