This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Triton Repository". The branch, master has been updated via 3787341e422c6d143cdb6c770569f3c7f1d7714d (commit) from cf4cfbc4dda0fa197c4f5cc18309dcaf1585aaa5 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 3787341e422c6d143cdb6c770569f3c7f1d7714d Author: Kevin Harms <[email protected]> Date: Tue Feb 28 02:31:39 2012 -0600 Minor edits to client-fault-handling.txt for spelling ----------------------------------------------------------------------- Summary of changes: code/doc/resilience/client-fault-handling.txt | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) Diff of changes: diff --git a/code/doc/resilience/client-fault-handling.txt b/code/doc/resilience/client-fault-handling.txt index 4a32c43..da22561 100644 --- a/code/doc/resilience/client-fault-handling.txt +++ b/code/doc/resilience/client-fault-handling.txt @@ -46,7 +46,7 @@ times for requests over time and use this information to calculate appropriate timeout values for future operations. The actual client communication logic will simply query the traffic cop on each operation to determine how long it should wait for a response. If a response is not -received, then the traffic is consulted to determine whether the client +received, then the traffic cop is consulted to determine whether the client should retry to the same server, retry to a different server, or refresh its system state information. The traffic cop is a centralized location for local policy decisions and may use information from a variety hooks/post-receive -- Triton Repository