On 4 June 2010 21:28, Tobie Langel <tobie.lan...@gmail.com> wrote: >> It may be just a case of the code and the documentation not agreeing >> and no comments saying that the second parameter is deprecated. > > Right on. I also wasn't aware it was documented for Responders. We > never marked it deprecated for ajax callbacks, as it never actually > was documented.
This whole exercise has been useful though. I didn't quite get the difference between headerJSON and responseJSON. Both of which are extremely useful. headerJSON for the status (data retrieved, errors, etc.) and responseJSON the the content (data, error messages, etc.) from the server side app. Excellent stuff! Regards, Richard. -- ----- Richard Quadling "Standing on the shoulders of some very clever giants!" EE : http://www.experts-exchange.com/M_248814.html EE4Free : http://www.experts-exchange.com/becomeAnExpert.jsp Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 ZOPA : http://uk.zopa.com/member/RQuadling -- You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en
