RequestOptions provides a way to set certain control arguments to send to the server like a per-request timeout or batch size. For bytecode traversals, these are set somewhat statically and selectively by way of with() which are then gathered by DriverRemoteConnection into a RequestOptions object and then sent to the server on the request - it's basically leading to a giant switch statement as new special options are being added.
Perhaps we should also consider a "request headers" space on the RequestMessage rather than just throwing all these options in at the "args" level.
Another idea might be to do with(TraversalSourceOptions) where TraversalSourceOptions would be a new interface that something like RequestOptions could implement. That way we could pass around RequestOptions in a consistent way: