anchor.diff:  
   === Health Checking
   
  -The status of a backend is checked in a separate goroutine that runs
  -until the proxy exits.  That status is simplistic currently, essentially
  -whether or not the backend can process a SQL statement determines
  -whether the health of the backend is good or bad.  This health check
  -is performed every few seconds on each backend.
  +The status of a backend is checked in a separate goroutine that runs until the proxy exits.  
   
  -As the status of a backend changes, the global configuration is
  -updated.  The backend status checked by the active connection
  -processing to determine which backends are available to process
  -a SQL statement.
  +The status health check is currently a simple implementation - essentially determining only whether the backend can process a SQL statement.  
   
  -Health status is captured and placed into an event channel.  The event
  -channel is used to publish events to any number of subscribers to the
  +This health check is performed every few seconds on each backend.
  +
  +As the status of a backend changes, the global configuration is updated.  The backend status checked by the active connection processing in order to 
  +determine which backends are available to processa SQL statement.
  +
  +Health status is captured and placed into an event channel.  The event channel is used to publish events to any number of subscribers to the
   REST API.
   
   == Legal Notices
  
positive.code: 
  === Connection Pooling
  
  Each backend (master and replica(s)) that is defined in the proxy 
  configuration file has a connection pool provisioned for it.  
  The connection pool is a fixed size currently and established before 
  the proxy begins to accept connections from clients.
  
  The connections in the pool are determined by the pool settings
  found within the configuration parameters *credentials* and *pool*.
  
  Currently only a basic PostgreSQL authentication is allowed using
  username and password.
  
  As client requests come into the proxy, the proxy will choose
  which backend to route the SQL statement to, then pick a free 
  connection from the backend's connection pool.
  
  For each connection pool there is a golang channel defined to
  manage which connections are available for use when processing a SQL
  statement.  After the SQL statement is processed, the connection is
  returned to the pool.  You can think of the pool's channel as a 
  queue of available connections.
  
  === Client Authentication
  
  Each client must authenticate against the master backend before the
  proxy will process future client requests.  The proxy does not include
  an authentication store itself, but instead relies on the master
  backend to perform authentication.
  
  Once a client does authenticate, the proxy will terminate the client's
  connection to the master and subsequently begin using the connections
  from the connection pools.
  
  === Annotations
  
  SQL statements that include a SQL comment of a particular format
  will be used to determine the routing of a SQL statement either to
  a master or a replica.
  
  This formatted comment can appear anywhere in a SQL statement but
  it is generally better to place it at the front of the SQL statement
  to be easy to read and locate.
  
  If an annotation is not found in a SQL statement, the the SQL statement
  is assumed to routed to the master by default.
  
  Examples of annotations look like this:
  ....
  
negative.code: = Developer Guide - Crunchy Proxy
  Crunchy Data Solutions, Inc.
  v0.0.1, {docdate}
  image::crunchy_logo.png?raw=true[]
  
  == Building
  
  Assuming an installation directory of *$HOME/gdev*, please follow the following steps to build *crunchy proxy* from source:
  ....
  mkdir -p $HOME/gdev/src $HOME/gdev/pkg $HOME/gdev/bin
  export GOPATH=$HOME/gdev;export GOBIN=$GOPATH/bin;export PATH=$PATH:$GOBIN
  ....
  
  First, install a golang compiler. As an example, it is possible to:
  ....
  sudo yum -y install golang 
  ....
  
  Next, pull the source code as follows:
  ....
  cd gdev/src
  go get github.com/tools/godep
  