E.g. A list of column names would encode in a query string as 'c=column_a&c=column_b' etc. But more efficient would be: "c=ab" (one character per selected column) or even "c=3" (yay for bit flags).
@ayo Hmmm, I wonder if there's any tools I could help someone build that'd help you tidy up that mess...
@ayo What does that have to do with JS? Granted, client-side routing never made much sense to me, I don't see anything preventing it to be done server-side.
@wasamasa The naive and long query parameters can be generated through <form method="get">. That'll not work with custom encodings.
@ayo Thank you, that makes more sense. I can imagine some workarounds, but nothing less icky. Somehow I suspect the web doesn't exactly lend itself to complex user interfaces...
Send it via POST so that people don't see this mess :P
Welcome to your niu world ! We are a cute and loving international community Ｏ(≧▽≦)Ｏ !