anchor.diff:  A `:remote` created in the following fashion will be "sessionless", meaning each script issued to the server with
   `:>` will be encased in a transaction and no state will be maintained from one request to the next.
   
  -[gremlin-groovy]
  -----
  -:remote connect tinkerpop.server conf/remote-objects.yaml
  +[source,groovy]
  +----
  +gremlin> :remote connect tinkerpop.server conf/remote-objects.yaml
  +==>Configured localhost/127.0.0.1:8182
   ----
   
   In other words, the transaction will be automatically committed (or rolledback on error) and any variables declared
  
positive.code: :> x = 1
  :> y = 2
  :> x + y
  ----
  
  With the above command a session gets created with a random UUID for a session identifier. It is also possible to
  
negative.code: y = 2
  x + y
  :remote console
  :remote close
  ----
  
  In the above example, the `:remote console` command is executed. It places the console in a state where the `:>` is
  