> headerJSON for the status (data retrieved, errors, etc.) and
> responseJSON the the content (data, error messages, etc.) from the
> server side app.
Yes, headerJSON is particularly useful combined to HTML in the
response body.
--
You received this message because you are subscribed to the Goog
On 4 June 2010 21:28, Tobie Langel 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 callback
> 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.
Best,
To
On 2 June 2010 23:06, Tobie Langel wrote:
> It's been deprecated in favor of Ajax.Response#headerJSON.
>
> Best,
>
> Tobie
>
> --
> 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@googlegrou
It's been deprecated in favor of Ajax.Response#headerJSON.
Best,
Tobie
--
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
proto
