summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Adam Chlipala <adam@chlipala.net>2013-12-25 12:02:42 -0500
committerGravatar Adam Chlipala <adam@chlipala.net>2013-12-25 12:02:42 -0500
commit919e33bbf5f613fb6fcade1f88b33347a6aae1c1 (patch)
treedfd6cc6e1f872ecb2b844ffaa6dcf24c134577f3 /doc
parentf42ed389d1b67749ff441c6389f7fcf14237c211 (diff)
Add a bit of manual clarification about channels and clients
Diffstat (limited to 'doc')
-rw-r--r--doc/manual.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/manual.tex b/doc/manual.tex
index 968d93eb..9bc52f4c 100644
--- a/doc/manual.tex
+++ b/doc/manual.tex
@@ -2194,7 +2194,7 @@ $$\begin{array}{l}
\mt{val} \; \mt{self} : \mt{transaction} \; \mt{client}
\end{array}$$
-\emph{Channels} are the means of message-passing. Each channel is created in the context of a client and belongs to that client; no other client may receive the channel's messages. Each channel type includes the type of values that may be sent over the channel. Sending and receiving are asynchronous, in the sense that a client need not be ready to receive a message right away. Rather, sent messages may queue up, waiting to be processed.
+\emph{Channels} are the means of message-passing. Each channel is created in the context of a client and belongs to that client; no other client may receive the channel's messages. Note that here \emph{client} has a technical Ur/Web meaning so that it describes only \emph{single page views}, so a user following a traditional link within an application will remove the ability for \emph{any} code to receive messages on the channels associated with the previous client. Each channel type includes the type of values that may be sent over the channel. Sending and receiving are asynchronous, in the sense that a client need not be ready to receive a message right away. Rather, sent messages may queue up, waiting to be processed.
$$\begin{array}{l}
\mt{con} \; \mt{channel} :: \mt{Type} \to \mt{Type} \\