From 05009329cf9e5ad8601b01844716d6d5ed244daa Mon Sep 17 00:00:00 2001
From: Paul Arthur <paul.arthur@flowerysong.com>
Date: Tue, 11 Jun 2013 12:37:58 -0400
Subject: Add naive compaction for Query serialization

Can be very efficient with the right input, but probably has
degenerative cases where it increases the size. Worst-case size
increase is one character per ID in the result set, so it shouldn't be
an issue.

String lengths for a large search result that was unstorable before:
serialize: 1991874
json_encode: 756249
cooked: 244

And some with more discontinuity:
serialize: 1772238
json_encode: 674751
cooked: 37950

serialize: 164942
json_encode: 65771
cooked: 25369
---
 browse.php | 1 +
 1 file changed, 1 insertion(+)

(limited to 'browse.php')

diff --git a/browse.php b/browse.php
index ed8b94be..e5994c38 100644
--- a/browse.php
+++ b/browse.php
@@ -63,6 +63,7 @@ switch($_REQUEST['action']) {
         $browse->show_objects();
     break;
     case 'tag':
+        //FIXME: This whole thing is ugly, even though it works.
         $browse->set_sort('count','ASC');
         // This one's a doozy
         $browse->set_simple_browse(false);
-- 
cgit