anchor.diff:  |timeout |Specifies the length of time in milliseconds that the remote will wait for a response from the server.
   |=========================================================
   
  +[[console-aliases]]
  +Aliases
  +^^^^^^^
  +
   The `alias` configuration command for the Gremlin Server `:remote` can be useful in situations where there are
   multiple `Graph` or `TraversalSource` instances on the server, as it becomes possible to rename them from the client
   for purposes of execution within the context of a script.  Therefore, it becomes possible to submit commands this way:
  
positive.code: WARNING: Transactions on graphs in initialization scripts are not closed automatically after the script finishes
  executing.  It is up to the script to properly commit or rollback transactions in the script itself.
  
  With Gremlin Server running it is now possible to issue some scripts to it for processing.  Start Gremlin Console as follows:
  
  [source,text]
  ----
  
negative.code: :remote config alias x g
  :> x.E().label().groupCount()
  ----
  
  [[console-sessions]]
  Sessions
  ^^^^^^^^
  
  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
  ----
  
  In other words, the transaction will be automatically committed (or rolledback on error) and any variables declared
  in that script will be forgotten for the next request. See the section on <<sessions, "Considering Sessions">>
  for more information on that topic.
  
  To enable the remote to connect with a session the `connect` argument takes another argument as follows:
  
  [gremlin-groovy]
  ----
  :remote connect tinkerpop.server conf/remote.yaml session
  :> 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
  assign a custom session identifier by adding it as the last argument to `:remote` command above.
  
  [[connecting-via-java]]
  Connecting via Java
  