Works for puts, gets and transactions andthem also within functions.This solution allows to limit the number of threadshandling client requests in a server waiting fora response from a given server.For example, if we configure the system to allowat max 1/2 of the available threads to handle client requestsbusy towards a given server, supposing we have a4 servers system with MAX_THREADS=8, if at a given pointin time server1 has 4 threads busy waiting to get aresponse from server2 and another request comes to server1that would require to communicate with server2,the request will be rejected.This feature could be used in situations when a server is not respondingor is responding slowly in order to limit the number of serverthreads (in the rest of servers) to handle client requests that arebusy waiting for an answer from the problematic server.This way, even if a server is not responding or is being veryslow, there will always be some threads available to handleclient requests in the healthy servers.As a result, a non-responding server would not eventuallyprovoke a 100% traffic loss.In order to implement this feature, a new observer typehas been created (SendReceiveMessageObserver).Calls to this observer have been added beforea put, get or transaction needs to go to another server(before any change has been made locally) andafter the response has been received.With a particular implementation of this observer(see GenericDunitTest.MySendReceiveMessageObserver)that keeps track of the number of threads waiting foran answer to each servers, operations may be rejectedif the limit has been surpassed.In GenericDUnitTest that observer is set in theservers and the functionality can be testedmanually by looking at the logs.Some refactorings and renamings

…d add function to sanctioned data serializables