Surfin Safari

Scott wrote:
> Assuming that Joyce has rolled the changes out to the live site...it
> looks like the "nopost" option isn't having much effect on Safari.
> I still get the infinitely blue tunnel. Did we increase the buffer
> flush size? (Or add the option to the JS client?)

We did not increase the buffer size on the code we checked in,
though I don't remember why.  Ben, do you?

Also, Ben, does a client app have to do anything special to use
the nopost option?

Joyce wrote:
> I did roll out the changes to the live site.  There were issues with the
> make process, specifically Doxygen, but I believe they occurred after the
> javascript client got built.

Yeah, JavaScript client gets built before the doxygen docs.
I'm looking on the site -- looks like you have the most up-to-date
client build.

Mike wrote:
> > Added kn_options=nopost which uses GET rather than POST to submit requests.
> But, but, that's not RESTful!! <whimper>

It's a hack to figure out where Safari/Konqueror's sticking points are.
Once we understand more we'll be able to evolve to Do The Right Thing.
Right now, Safari and Konqueror are blocking us from streaming data to
them in a timely fashion, so a hack is better than nothing at all...

In theory, at least...

   Adam



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01