bumping version to 0.3.5
expand short syntax to work with nested method calls\!
update documentation for short syntax
Make the CaSH CLI respect the noninteractive password input
add note to use TAB for completion in CaSH
remove extra space
Add chronologizetest to suite
CON-72: Fix transaction deadlock

This commit fixes a bug that caused a deadlock when committing a transaction
that wrote a key as a value and subsequently performed a query against the
key that included the value
Revert "Add chronologizetest to suite"

This reverts commit 05c94630c6c02f7f7e719b51fa2faa9e764ca9e7.
update test suite
CON-75: Add custom List to hold the Buffer pages

This commit implements a custom List to hold the pages in the Buffer.
In particular, the custom list fully delegates to a Java ArrayList
except for the iterator() method. Instead, the custom List implements
a custom iterator that has the ability to "reload" in the background
if items are added to the underlying collection from outside the iterator.
This essentially means we don't see ConcurretModificationExceptions, which
is okay since the underlying collection can only see new data (as opposed
to seeing existing data deleted) while a reader is using the iterator

Conflicts:
	concourse-server/src/test/java/org/cinchapi/concourse/server/storage/temp/BufferTest.java
javadoc update
CON-82: Don't crap out on corrupt transaction recovery

This commit prevents the recovery of a corrupt transaction
from preventing server startup.

1. Add better logging about block syncing
2. Add better logging about when transaction recovery actually happens
3. Gracefully handle the case when we try to recover a corrupt transaction

Conflicts:
	concourse-server/src/main/java/org/cinchapi/concourse/server/storage/db/Database.java
more logging
lazily load block index
cleanup

Conflicts:
	concourse-integration-tests/src/test/java/org/cinchapi/concourse/ClearTest.java
Add functionality to get the database backing store and make
sure that we normalize the file paths in the BlockLoader
CON-83: Prevent data duplication during unexpected shutdowns

This commit makes some changes to the server startup logic to
detect cases when there might be duplicate data when the server
restarts after a crash. Duplicate data would occur if the server
crashed after one or more blocks was synced but before the corresponding
buffer page was deleted. The changes contained within try to detect
those possibilities by checking for balanced blocks and also
verifying that transported Writes are acceptable upon initial startup

Conflicts:
	concourse-server/src/main/java/org/cinchapi/concourse/server/storage/db/Database.java
	concourse-server/src/test/java/org/cinchapi/concourse/server/storage/EngineTest.java
Use checksums to prevent loading blocks with duplicate data
add TLists