Front End Speed Tweak: Speed up $.post() callback by returning before booting up drupal

I've been playing a bit with the patch, and it does improve the front end loading speed, but not as much as I would have thought: locally, in a non-loaded environment but using DNS resolution, the callback time goes down from ~90ms to ~65ms, including about 25ms DNS lookup. That's still a 33% performance improvement as far as end users are concerned, and nothing in the wild is using the json information returned by the callback right now, so, that looks good.

(By the way, Content-Length: 13 is the right thing to include the carriage return :-))

The only thing I'm wondering about that makes me put this back to CNW is the use of the ignore_user_abort() function. According to the documentation, called this way, without argument, it's supposed to only return the current value, without changing it, and the code does nothing with the return value, so I'm a bit lost about the use case. Should it be ignore_user_abort(TRUE); ? Or is the documentation on php.net somehow wrong ?

Re-reading the code right before commiting it, there's another thing I'm wondering about: is there a specific reason to call header('Connection: close'); twice, once before ob_start and once after it ? Isn't the second call enough ?

Okay, I've just pushed db7ef78, which is your patch with only one Connection: Close header (there's no other header to override) and with ignore_user_abort(TRUE).

The input buffering code does seems to have an impact, it looks like cURL doesn't close the connection without it. I'm not sure completely sure it's not just the three flush more than the output buffer, but I've left it as is, at least that way it's easier to keep in sync with your project :-)

So, the only thing left to say is Thanks for the patch, and for trying out jStats !

Sure, after two nice git cherry-pick there's now 93c3062d in the 6.x-1.x branch.