Simon Thulbourn
added a comment - 19/Aug/09 16:32 Here's a patch that changes it globally for 30 days, but I'm unsure if it's needed, I found out that futon does this already for a database during a session. I guess I've just never noticed it.

Alexander Shorin
added a comment - 22/Feb/12 02:50 Reproduced using Firefox 10.0, Chromium 18.0.1025.33, Opera 11.61 and 12.00 alpha, on Linux x86_64 against CouchDB 1.0.2 release, 1.2.0a-0d8ddc8-git and 1.3.0a-32a67c1-git.
Same thing on Windows for Chrome 16.0.912.75 and IE-8 against same CouchDB instances.
For all cases rows-per-page value was keeped only for current tab session. Or what I'm doing wrong?(:

Sam Bisbee
added a comment - 22/Feb/12 02:58 Bah, now I'm seeing it happen on a different computer/browser combo: the rows-per-page is sticking for individual database pages, but does not carry over to all database pages.
Sounds like a classic case of not just browser support but different browser/OS configurations.
I'll hack something together tonight that uses cookies.

Sam Bisbee
added a comment - 22/Feb/12 03:54 This patch tells Futon's "storage system" to store per_page in the cookie instead of `window`.
The patch is also available on my github branch: https://github.com/sbisbee/couchdb/commit/e372836692f41926e56ec4d78d03b9fda364f09e
Cheers.

James Howe
added a comment - 29/Feb/12 11:35 A good system is to use window.localStorage if it's defined, and fallback to cookies if it isn't. This keeps the request headers free from unnecessary data that the server doesn't care about.

I don't disagree, but that's not how the futon storage system current works. It uses either memory (the window object) or cookies. It could be extended to support localStorage, but that's for another ticket.

Sam Bisbee
added a comment - 17/Mar/12 19:27 Hi James,
I don't disagree, but that's not how the futon storage system current works. It uses either memory (the window object) or cookies. It could be extended to support localStorage, but that's for another ticket.
Cheers.