anchor.diff:  the "g" provided to the `DriverRemoteConnection` corresponds to the name of a `GraphTraversalSource` on the remote end.
   
   [source,python]
  +----
   g = traversal().withRemote(DriverRemoteConnection('ws://localhost:8182/gremlin','g'))
  +----
   
   If you need to send additional headers in the websockets connection, you can pass an optional `headers` parameter
   to the `DriverRemoteConnection` constructor.
   
   [source,python]
  +----
   g = traversal().withRemote(DriverRemoteConnection('ws://localhost:8182/gremlin','g',headers={'Header':'Value'}))
  +----
   
   [[python-imports]]
   === Common Imports
  
positive.code: language's JSR-223 `ScriptEngine` implementation.
  
  [source,java]
  g.V().out("knows").map(Lambda.function("it.get().value('name') + ' is the friend name'"))
  g.V().out("knows").sideEffect(Lambda.consumer("println it"))
  g.V().as("a").out("knows").as("b").select("b").by(Lambda.<Vertex,Integer>function("it.value('name').length()"))
  
  Finally, Gremlin `Bytecode` that includes lambdas requires that the traversal be processed by the
  `ScriptEngine`. To avoid continued recompilation costs, it supports the encoding of bindings, which allow Gremlin
  
negative.code: server configuration can be managed by the `alias` method on `Client` as follows:
  
  [source,java]
  ----
  Client g1Client = client.alias("g1")
  Client g2Client = client.alias("g2")
  g1Client.submit("g.V()")
  g2Client.submit("g.V()")
  ----
  
  The above code demonstrates how the `alias` method can be used such that the script need only contain a reference
  to "g" and "g1" and "g2" are automatically rebound into "g" on the server-side.
  