clarify lock behaviour for non-existent keysupdate javadoc for IMap.lock(K)
closes #1200
TTL documentation correction.

TTL documentation correction.
Fixed bug while reading client buffer when reached end of multiple packets inside the same buffer run
Moved deserialization from future.set to future.get

This way the operation service is not bothered wit deserialziation.

I also added a test which verifies that we should get copies. But appearently we are not. I
need to have a chat with Mehmet how this can be prevented.
Rename of the Test class
Improved testing
Removed invalid commment
Test cleanup
Cleanup in the way the response is resolved so that it is shared
between the normal future.get and the async.andthen stuff.
Resolved merged conflict
Added missing attribute copy
fixes issue #1863
fixes issue #1863 tests
Lowered count to make it finish in time
Merge pull request #1926 from noctarius/fixed-client-connection-buffer-read2

Fixed bug while reading client buffer when reached end of multiple packe...
Merge pull request #1928 from ahmetmircik/fixIssue1863

Fixes issue #1863
Merge pull request #1855 from pveentjer/spi-future-serialization

Moved deserialization from future.set to future.get
Merge pull request #1775 from sworisbreathing/update-documentation

clarify lock behaviour for non-existent keys
Hosted MC documentation improvements
fixes randomly failing tests