Skip to content

Commit 1ba6662

Browse files
committed
rfc42: add optional subprocess labels
Problem: There is no convenient way to refer to subprocesses launched using the protocol specified in RFC 42. Introduce an optional subprocess label which, when specified, can be used to refer to a subprocess by name instead of PID.
1 parent c315196 commit 1ba6662

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

spec_42.rst

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -325,6 +325,11 @@ The :program:`kill` RPC sends a signal to a remote process.
325325

326326
(*integer*, REQUIRED) The signal number.
327327

328+
.. object:: label
329+
330+
(*string*, OPTIONAL) The label of the remote process. If this key is
331+
set in the payload then the value of ``pid`` SHALL be ignored.
332+
328333
.. object:: kill response
329334

330335
The successful response SHALL contain no payload.
@@ -392,6 +397,17 @@ the following keys:
392397
SHALL be transmitted to client channel. Messages received on the client
393398
channel SHALL be transmitted to this URI.
394399

400+
.. object:: label
401+
402+
(*string*, OPTIONAL) A string label for the command.
403+
404+
If present, the label SHALL NOT be empty.
405+
406+
The server SHOULD allow processes to be referenced by label in
407+
addition to process ID.
408+
409+
The server MUST reject attempts to create processes with duplicate
410+
labels.
395411

396412
I/O Object
397413
==========

0 commit comments

Comments
 (0)