Todd Wang | 0d12d71 | 2014-10-06 17:25:41 -0700 | [diff] [blame] | 1 | // This file was auto-generated via go generate. |
| 2 | // DO NOT UPDATE MANUALLY |
| 3 | |
| 4 | /* |
| 5 | The vrpc tool facilitates interaction with Veyron RPC servers. In particular, |
| 6 | it can be used to 1) find out what API a Veyron RPC server exports and |
| 7 | 2) send requests to a Veyron RPC server. |
| 8 | |
| 9 | Usage: |
| 10 | vrpc <command> |
| 11 | |
| 12 | The vrpc commands are: |
| 13 | describe Describe the API of an Veyron RPC server |
| 14 | invoke Invoke a method of an Veyron RPC server |
| 15 | help Display help for commands or topics |
| 16 | Run "vrpc help [command]" for command usage. |
| 17 | |
| 18 | The global flags are: |
| 19 | -alsologtostderr=true: log to standard error as well as files |
| 20 | -log_backtrace_at=:0: when logging hits line file:N, emit a stack trace |
| 21 | -log_dir=: if non-empty, write log files to this directory |
| 22 | -logtostderr=false: log to standard error instead of files |
| 23 | -max_stack_buf_size=4292608: max size in bytes of the buffer to use for logging stack traces |
| 24 | -stderrthreshold=2: logs at or above this threshold go to stderr |
| 25 | -v=0: log level for V logs |
| 26 | -vmodule=: comma-separated list of pattern=N settings for file-filtered logging |
| 27 | -vv=0: log level for V logs |
| 28 | |
| 29 | Vrpc Describe |
| 30 | |
| 31 | Describe connects to the Veyron RPC server identified by <server>, finds out what |
| 32 | its API is, and outputs a succint summary of this API to the standard output. |
| 33 | |
| 34 | Usage: |
| 35 | vrpc describe <server> |
| 36 | |
| 37 | <server> identifies the Veyron RPC server. It can either be the object address of |
| 38 | the server or an Object name in which case the vrpc will use Veyron's name |
| 39 | resolution to match this name to an end-point. |
| 40 | |
| 41 | Vrpc Invoke |
| 42 | |
| 43 | Invoke connects to the Veyron RPC server identified by <server>, invokes the method |
| 44 | identified by <method>, supplying the arguments identified by <args>, and outputs |
| 45 | the results of the invocation to the standard output. |
| 46 | |
| 47 | Usage: |
| 48 | vrpc invoke <server> <method> <args> |
| 49 | |
| 50 | <server> identifies the Veyron RPC server. It can either be the object address of |
| 51 | the server or an Object name in which case the vrpc will use Veyron's name |
| 52 | resolution to match this name to an end-point. |
| 53 | |
| 54 | <method> identifies the name of the method to be invoked. |
| 55 | |
| 56 | <args> identifies the arguments of the method to be invoked. It should be a list |
| 57 | of values in a VOM JSON format that can be reflected to the correct type |
| 58 | using Go's reflection. |
| 59 | |
| 60 | Vrpc Help |
| 61 | |
| 62 | Help with no args displays the usage of the parent command. |
| 63 | Help with args displays the usage of the specified sub-command or help topic. |
| 64 | "help ..." recursively displays help for all commands and topics. |
| 65 | |
| 66 | Usage: |
| 67 | vrpc help [flags] [command/topic ...] |
| 68 | |
| 69 | [command/topic ...] optionally identifies a specific sub-command or help topic. |
| 70 | |
| 71 | The help flags are: |
| 72 | -style=text: The formatting style for help output, either "text" or "godoc". |
| 73 | */ |
| 74 | package main |