anchor.diff:  As such, there will be no data on the disk that is accessible. For instance, there is no more `~reducing`, `~traversers`,
   and specially named side-effects such as `m` from a `groupCount('m')`. The data is still accessible via `ComputerResult.memory()`,
   it simply does not have a corresponding on-disk representation.
  +
  +RemoteGraph
  +^^^^^^^^^^^
  +
  +`RemoteGraph` is a lightweight `Graph` implementation that acts as a proxy for sending traversals to Gremlin Server for
  +remote execution. It is an interesting alternative to the other methods for connecting to Gremlin Server in that all
  +other methods involved construction of a `String` representation of the `Traversal` which is then submitted as a script
  +to Gremlin Server (via driver or REST).
  +
  +[source,groovy]
  +----
  +gremlin> graph = RemoteGraph.open('conf/remote-graph.properties')
  +==>remotegraph[DriverServerConnection-localhost/127.0.0.1:8182 [graph='graph]]
  +gremlin> g = graph.traversal()
  +==>graphtraversalsource[remotegraph[DriverServerConnection-localhost/127.0.0.1:8182 [graph='graph]], standard]
  +gremlin> g.V().valueMap(true)
  +==>[name:[marko], label:person, id:1, age:[29]]
  +==>[name:[vadas], label:person, id:2, age:[27]]
  +==>[name:[lop], label:software, id:3, lang:[java]]
  +==>[name:[josh], label:person, id:4, age:[32]]
  +==>[name:[ripple], label:software, id:5, lang:[java]]
  +==>[name:[peter], label:person, id:6, age:[35]]
  +----
  +
  +Note that `g.V().valueMap(true)` is executing in Gremlin Server and not locally in the console.
  +
  +See: link:https://issues.apache.org/jira/browse/TINKERPOP-575[TINKERPOP-575],
  +link:http://tinkerpop.apache.org/docs/3.2.0-incubating/reference/#connecting-via-remotegraph[Reference Documentation - Remote Graph]
   
   Upgrading for Providers
   ~~~~~~~~~~~~~~~~~~~~~~~
  
positive.code: 
  * `VertexComputeKeys` can be marked transient and must be removed from the resultant `ComputerResult.graph()`.
  
  See link:https://issues.apache.org/jira/browse/TINKERPOP-1166[TINKERPOP-1166]
  
  Operational semantic test cases have been added to `GraphComputerTest` to ensure that all the above are implemented correctly.
  
  
negative.code: accommodate a new API that reflects the `Memory` updates above. This should be a simple change. Note that `FinalGet`
  no longer exists and such post-reduction processing is handled by the reducing step (via the new `Generating` interface).
  
  See: link:https://issues.apache.org/jira/browse/TINKERPOP-1164[TINKERPOP-1164]
  
  Graph Processor Providers
  ^^^^^^^^^^^^^^^^^^^^^^^^^
  