Add get entry with proof and get sth consistency.
Modified monitor so it works with AsyncLogClient.
get_entries is now sending multiple queries.
Test change.
Updating akamai branch of Certificate Transparency with all the changes need to run in the akamai setting.  Will probably no longer compile with just CT instructions.
Adding some test input files. Readme type information.  Modified scripts.
Add a config query table to reflect config message. It's more code then you would expect since I need to extract key/value pairs as strings from the protobuf message.  Now you can fields in the message and they'll just show up in the query table.  No extra code needed.
Git experiment.
ct-server running again without akamai.  httpconnect modified to run with and without akamai with latest changes.
Small change to server string.
Check for expired peer should be in ms, not seconds.  We unfortunately mix ms and seconds because the sct's timestamp is in ms, but the flags are in seconds.
Small changes to test scripts to work on my desktop.
Killed query.  Fixed.  By putting it in if for akamai run, it was the query event was getting destroyed on exit of if.
Some small changes to work with akamai.  Stress_test script is modification of test_running_server that hits 2 ct instances to see if they communicate properly.
Harmonizing some naming conventions.  No real functionality changes.
Max DB entry size should revert to DB limit if config set back to 0. Also fixed a problem that a peer was appearing as removed and active after I rand the removed peer removal from the db_tool.  Modified code to only remove the indexes of peers who appear only in removed as a safety check.  All removed peers get taken out of list though after done.  Not sure why it happened.
Fix unit tests.  Modified sleep for DB key/cert to break out and fail if sleep is set to 0.
Enhanced unit tests to increase coverage.
Bug where db_limit_max_entry_size wasn't initialized.  Now set to current DB limit.  In reality it'll be set when CT starts up, but for unit tests, need to set it to something relatively large.
Modified clear_removed_peers to pass in peers whose index has really been removed.  This is to counter the problem where the db_tool has gotten the peers and removed the indexes of the removed_peers.  But it takes long enough that new peers are placed in the removed_peers set, but have not yet had their indexes removed.