On Sep 10, 11:32 pm, chrysanthe m <[email protected]> wrote: > Hi Dave > Yes. > I know I should not be shoveling out so much data to the client, but I have > to for this proof of concept and will restrict it in production. Has anyone > parsed return json data larger than 8K?
I did. Note that: - I am using the response body (responseJSON) and not the response header. - I noticed that my server uses "Transfer-Encoding: chunked" (in case it may have an effect, since for shorter replies it uses "gzip" and give a Content-Length) . HTH Eric > > On Thu, Sep 2, 2010 at 9:27 AM, Dave Kibble <[email protected]> wrote: > > just going on the number 8k (IE limit) and the ambiguity of "return": do > > you mean that ajax fails when sending >8k to the server, or when the reply > > to an ajax request from the server is >8k > > > -- > > 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 protected]. > > To unsubscribe from this group, send email to > > [email protected]<prototype-scriptaculous%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/prototype-scriptaculous?hl=en. > > -- 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 protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
