Mercurial > urweb
comparison doc/manual.tex @ 914:782f0b4eea67
New release
| author | Adam Chlipala <adamc@hcoop.net> |
|---|---|
| date | Tue, 25 Aug 2009 17:33:13 -0400 |
| parents | 2faf558b2d05 |
| children | 28bf725de7f3 |
comparison
equal
deleted
inserted
replaced
| 913:b26823138bf8 | 914:782f0b4eea67 |
|---|---|
| 1792 \mt{val} \; \mt{dyn} : \mt{use} ::: \{\mt{Type}\} \to \mt{bind} ::: \{\mt{Type}\} \to \mt{unit} \\ | 1792 \mt{val} \; \mt{dyn} : \mt{use} ::: \{\mt{Type}\} \to \mt{bind} ::: \{\mt{Type}\} \to \mt{unit} \\ |
| 1793 \hspace{.1in} \to \mt{tag} \; [\mt{Signal} = \mt{signal} \; (\mt{xml} \; \mt{body} \; \mt{use} \; \mt{bind})] \; \mt{body} \; [] \; \mt{use} \; \mt{bind} | 1793 \hspace{.1in} \to \mt{tag} \; [\mt{Signal} = \mt{signal} \; (\mt{xml} \; \mt{body} \; \mt{use} \; \mt{bind})] \; \mt{body} \; [] \; \mt{use} \; \mt{bind} |
| 1794 \end{array}$$ | 1794 \end{array}$$ |
| 1795 | 1795 |
| 1796 Transactions can be run on the client by including them in attributes like the $\mt{Onclick}$ attribute of $\mt{button}$, and GUI widgets like $\mt{ctextbox}$ have $\mt{Source}$ attributes that can be used to connect them to sources, so that their values can be read by code running because of, e.g., an $\mt{Onclick}$ event. | 1796 Transactions can be run on the client by including them in attributes like the $\mt{Onclick}$ attribute of $\mt{button}$, and GUI widgets like $\mt{ctextbox}$ have $\mt{Source}$ attributes that can be used to connect them to sources, so that their values can be read by code running because of, e.g., an $\mt{Onclick}$ event. |
| 1797 | |
| 1798 \subsubsection{Remote Procedure Calls} | |
| 1799 | |
| 1800 Any function call may be made a client-to-server ``remote procedure call'' if the function being called needs no features that are only available to client code. To make a function call an RPC, pass that function call as the argument to $\mt{Basis.rpc}$: | |
| 1801 | |
| 1802 $$\begin{array}{l} | |
| 1803 \mt{val} \; \mt{rpc} : \mt{t} ::: \mt{Type} \to \mt{transaction} \; \mt{t} \to \mt{transaction} \; \mt{t} | |
| 1804 \end{array}$$ | |
| 1797 | 1805 |
| 1798 \subsubsection{Asynchronous Message-Passing} | 1806 \subsubsection{Asynchronous Message-Passing} |
| 1799 | 1807 |
| 1800 To support asynchronous, ``server push'' delivery of messages to clients, any client that might need to receive an asynchronous message is assigned a unique ID. These IDs may be retrieved both on the client and on the server, during execution of code related to a client. | 1808 To support asynchronous, ``server push'' delivery of messages to clients, any client that might need to receive an asynchronous message is assigned a unique ID. These IDs may be retrieved both on the client and on the server, during execution of code related to a client. |
| 1801 | 1809 |