meta text protocol commands

- we get asked a lot to provide a "metaget" command, for various uses
(debugging, etc)
- we also get asked for random one-off commands for various use cases.
- I really hate both of these situations and have been wanting to
experiment with a slight tuning of how get commands work for a long
time.

Assuming that if I offer a metaget command which gives people the
information they're curious about in an inefficient format, plus data
they don't need, we'll just end up with a slow command with
compatibility issues. No matter how you wrap warnings around a command,
people will put it into production under high load. Then I'm stuck with
it forever.

Behold, the meta commands!

See doc/protocol.txt and the wiki for a full explanation and examples.

The intent of the meta commands is to support any features the binary
protocol had over the text protocol. Though this is missing some
commands still, it is close and surpasses the binary protocol in many
ways.

1 files changed, 2 insertions, 2 deletions

diff --git a/t/stats.t b/t/stats.t
index aa421ae..028a60a 100755
--- a/t/stats.t
+++ b/t/stats.t
@@ -26,9 +26,9 @@ my $stats = mem_stats($sock);
 # Test number of keys
 if (MemcachedTest::enabled_tls_testing()) {
     # when TLS is enabled, stats contains time_since_server_cert_refresh
-    is(scalar(keys(%$stats)), 71, "expected count of stats values");
+    is(scalar(keys(%$stats)), 72, "expected count of stats values");
 } else {
-    is(scalar(keys(%$stats)), 70, "expected count of stats values");
+    is(scalar(keys(%$stats)), 71, "expected count of stats values");
 }
 
 # Test initial state