Add Windows named-pipe local control
This commit is contained in:
parent
ce3e029b3d
commit
3c84713472
9 changed files with 338 additions and 72 deletions
|
|
@ -60,9 +60,10 @@ cover the subset intended as stable rather than every incidental field.
|
|||
|
||||
## Local Control JSONL
|
||||
|
||||
The local daemon control socket uses newline-delimited JSON request and response
|
||||
messages from `geth-control`. This protocol is local-only and not a remote trust
|
||||
boundary, but local automation may still rely on it.
|
||||
The local daemon control endpoint uses newline-delimited JSON request and
|
||||
response messages from `geth-control`. Its carrier is a Unix socket on
|
||||
Linux/macOS and a per-home Windows named pipe. This protocol is local-only and
|
||||
not a remote trust boundary, but local automation may still rely on it.
|
||||
|
||||
Stable local-control variants follow the same compatibility rules as `--json`
|
||||
output. Unknown variants, malformed JSON, and messages without a trailing
|
||||
|
|
|
|||
Loading…
Reference in a new issue