From 2555c24cbd50d7afc517f7c9e6cac77ba87f0d99 Mon Sep 17 00:00:00 2001
From: Adam Chlipala <adam@chlipala.net>
Date: Wed, 25 Dec 2013 12:02:42 -0500
Subject: Add a bit of manual clarification about channels and clients

---
 doc/manual.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'doc/manual.tex')

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} \\
-- 
cgit v1.2.3

