Renamed KVClientTest to BFTMapClientTest.
Replaced BFTMapClientTest with the latest version from the branch 185.

- Created default recoverable for classes implementing SingleRecoverable;
- Made changes to state transfer classes to work with single message processing.

Fixed bug in ServiceProxy. Replica was not re-sending unordered request as ordered after not matching reply;
Fixed some unused imports;
Changed tests to print log correctly.

Changed BFTMapImpl to implement SingleExecutable and Recoverable instead of use DefaultRecoverable.
Added tests on BFTMapImpl to test the size of serialization and time to serialize state.

Added a new demo named "BFTList", which is very similar to "BFTMap", but uses Lists instead of Maps.

Started changing the state transfer protocol to not perform checkpointing. Such procedure should be delegated to the applcation instead.

THIS IS AN UNSTABLE COMMIT!!!!!! USE AT OWN RISK!!!!!!!!!!!!!!!!!!

Started changing the state transfer protocol to not perform checkpointing. Such procedure should be delegated to the applcation instead.

THIS IS AN UNSTABLE COMMIT!!!!!! USE AT OWN RISK!!!!!!!!!!!!!!!!!!

Removed the methodes invoke(byte[], boolean readOnly) from ServiceProxy.
Fixed demo code to work with the new version of ServiceProxy.

Changed ServiceReplica to set the ReplyListener to null upon receive of invoke() call.

- Changed TOMMessageType from REQUEST and READONLY_REQUEST to ORDERED_REQUEST and UNORDERED_REQUEST respectively
- Added method in TOMSender to send messages to target replicas instead of send to all replicas

Fixed a bug on the Round object, that could have an updated array of processes in relation to the ServerViewManager. This bug would trigger an arrayoutofbound exception.

Added an optimization that decreases the leader change timeout upon a new view that removes the current leader from the group. There is also a debugging 'try-catch' on the "Round" class, that I'm using to track a bug that I couldn't resolve yet.

Updated the state transfer protocol to also include the latest view, in order to avoid delayed replicas from getting blocked after applying the state. If the view had changed in the middle of a state transfer and the view updates where already erased from the state log, the replica would alreays discard client requests, since they where for a view ahead of the one it had.

Also fixed a bug that wouldn't let the replica execute the requests contained in a state transfer log, also quase by the fact that a client might had a different view from the replica.

Fixed a bug that would manifest in a delayed replica: if a timeout occurred, the replica would be forever stopped, and the bug prevented it from triggering the state transfer protocol. With the bug gone, the replica will ask for the state.

Regarding the aforementioned bug, I added a parameter to the config file dubbed "timeoutHighmark". It should be lower than "paxosHighmark" and greater than "revivalHighmark". This will make the replica trigger the state transfer more quickly, given the conditions just described.

Fixed also a bug on the clients: when there were no "currentView" file, an exception would be thrown, and the clients would not read the host.config file. This no longer happens.

Finally, added some debugger messages in the leader change protocol and also in the servicereplica class.

Fixed a bug on the leader election. It didn't work well together with the reconfiguration. Modified the LC protocol plus the state transfer to fix this issue.

Small additions to the Throughput demo. Ir now has an option for DoS and shows the maximum throughput on the servers

 - ServiceReplica.receiveMessages() is now implementing the code for batch message processing;
 - BatchExecutable.executeBatch() signature was changed to has an array of MessageContext as parameter.

Fixed a bug on the leader change protocol that would block all replicas if the delayed replica triggered again a leader change before the others finished the same protocol.

Identified a bug on the method "send" of class NettyClientServerCommunicationSystemServerSide, but its cause remains misterious: if invoked 2 times for the same message (why it sometimes is invoked 2 times for the same message is not known), the client may not receive a reply on its end, and if no sufficent replies are received, the client blocks. If locks are used in this method, the problem seems to disappear.

Removed various locks from the leader change protocol which were rendered useless in previous commits.

The Proposed thread now  unlocks by this order: I am the leader -> the consensus as finished  -> I have message to order 

Now Executable is the top class. It has the executeUnordered method, as all executables can process readonly messages.
There are two classes extending Executable.
SingleExecutable has the executeOrdered method to process a sigle command.
BatchExecutable has the executeBatch to process multiple commands.
BatchExecutable was also changed to have a matrix of bytes as parameter, corresponding to an array of commands, having an array of bytes.
Demo classes was changed to use the new Executable structure.
ServiceReplica was also changed.

- Added tests for killing leaders;
- Added Logger to log tests in console;
- Added ConsoleTest to execute tests in Console window instead of JUnit.