Hi hipska, I was doing something a few weeks ago that required something other than responseText, and the easiest thing for me was to just look through the prototype.js file to see what is available. Now, don't take that to mean I believe it's *easy* for just anyone to look at that code and have it make sense. I'm not a javascript guru by any stretch of even the most wild imagination, but after a little study, it does start to make a little sense. Enough to figure out what you need to anyway.
Good luck! Phillip On Nov 30, 2007, at 4:18 AM, hipska wrote: > > Thanks for your reply, but it seems that this isn't working, or i'm > doing something wrong. > > Do you have a little example for me? > > On 30 nov, 10:19, "Gareth Evans" <[EMAIL PROTECTED]> wrote: >> there is responseJSON as well, set your http header content type to >> application/json and return the json string in the body of the >> request. >> If you screw it up it will be undefined. >> You should also use onSuccess instead of onComplete and you can >> check all >> the standard xmlhttprequest response object properties such as >> status and >> statusCode.http://www.prototypejs.org/api/ajax/request >> >> Gareth >> > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
