Skip to content

Commit 81c705c

Browse files
committed
Doc change suggestions from Carol
1 parent efbb295 commit 81c705c

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

docs/messaging.rst

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1092,10 +1092,12 @@ Message type: ``clear_output``::
10921092
Messages on the stdin ROUTER/DEALER sockets
10931093
===========================================
10941094

1095-
This is a socket where the request/reply pattern goes in the opposite direction:
1096-
from the kernel to a *single* frontend. Its purpose is to allow code to prompt
1097-
the user for a line of input, which would normally be read from stdin in a
1098-
terminal.
1095+
With the stdin ROUTER/DEALER socket, the request/reply pattern goes in the
1096+
opposite direction of most kernel communication.
1097+
With the stdin socket, the kernel makes the request, and the single frontend
1098+
provides the response.
1099+
This pattern allows code to prompt the user for a line of input,
1100+
which would normally be read from stdin in a terminal.
10991101

11001102
Many programming languages provide a function which displays a prompt, blocks
11011103
until the user presses return, and returns the text they typed before pressing
@@ -1143,7 +1145,7 @@ the user types.
11431145

11441146
.. note::
11451147

1146-
This model of requesting user input is quite different from how stdin works
1148+
This pattern of requesting user input is quite different from how stdin works
11471149
at a lower level. The Jupyter protocol does not support everything code
11481150
running in a terminal can do with stdin, but we believe that this enables the
11491151
most common use cases.

0 commit comments

Comments
 (0)