I have been playing around with PJAX after reading a mention of it in a description of how Basecamp got faster:
https://37signals.com/svn/posts/3112-how-basecamp-next-got-to-be-so-damn-fast-without-using-much-client-side-ui http://railscasts.com/episodes/294-playing-with-pjax https://github.com/defunkt/jquery-pjax The author can describe what it does better than me: "pjax loads HTML from your server into the current page without a full reload. It's ajax with real permalinks, page titles, and a working back button that fully degrades." After playing around for it for a bit, it definitely looks like this could be used to make websites snappier. Is anyone using this in production? Any know issues / gotchas to be aware of? Before I go any further, I would like to benchmark the site with and without PJAX, to have a sense of potential savings in page load time. Anyone have an idea how I could benchmark this? The javascript on the page has to be executed for pjax to kick-in. After some benchmarking, I think I would a/b test this on a production site to see if faster laod times increases conversions, which seems to be the consensus, but never hurts to measure for yourself, right?. Thanks for any pointers, -- Ylan -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
