===================================================================
RCS file: /home/cvs/OpenXM/doc/issac2000/ox-messages.tex,v
retrieving revision 1.1
retrieving revision 1.7
diff -u -p -r1.1 -r1.7
--- OpenXM/doc/issac2000/ox-messages.tex	2000/01/02 07:32:12	1.1
+++ OpenXM/doc/issac2000/ox-messages.tex	2000/01/16 06:02:41	1.7
@@ -1,6 +1,6 @@
-%%$OpenXM$
+%%$OpenXM: OpenXM/doc/issac2000/ox-messages.tex,v 1.6 2000/01/15 12:18:42 takayama Exp $
 
-\section{OX messages}  (Ohara)
+\section{OX messages}
 
 An OX message for TCP/IP is a byte stream consisting of
 a header and a body.
@@ -14,52 +14,36 @@ Header	& \hspace{10mm} Body \hspace{10mm} \\
 The header consists of two signed 32 bit integers.
 The first one is an OX tag 
 and the second one is a serial number of the OX message.
-Negative numbers are expressed by the two's complement.
+%Negative numbers are expressed by the two's complement.
 Several byte orders including the network byte order
 are allowed and the byte order is determined as a part of
-the establishment of a connection.
+the establishment of a connection. See Section \ref{secsession} for details.
 
-The OX messages are classifed into three types:
-DATA, COMMAND, and others.
-We have the following main tags for the OX messages.
+The OX messages are classified into three types:
+DATA, COMMAND, and SPECIAL.
+We have currently the following general tags for the OX messages.
 \begin{verbatim}
 #define	OX_COMMAND               513  // COMMAND
 #define	OX_DATA	                 514  // DATA
-#define OX_SYNC_BALL             515  // others
+#define OX_SYNC_BALL             515  // SPECIAL
 #define OX_DATA_WITH_LENGTH      521  // DATA
 #define OX_DATA_OPENMATH_XML     523  // DATA
 #define OX_DATA_OPENMATH_BINARY  524  // DATA
 #define OX_DATA_MP               525  // DATA
 \end{verbatim}
 
-New OX tags may be added.
+A new OX tag may be added.
 The new tag should be classified into DATA or COMMAND.
-For example, \verb+ OX_DATA_ASIR_BINARY +  was added a few month ago
-to send internal serialized objects of asir via OpenXM protocol.
-This is a tag classifed to DATA.
-See the home page of OpenXM to add a new tag.
+For example, \verb+ OX_DATA_ASIR_LOCAL_BINARY +  was added recently
+to send internal serialized objects of Asir via the OpenXM protocol.
+This is a tag classified to DATA.
+See the web page of OpenXM to add a new tag \cite{openxm-web}.
 
-In OpenXM, a distributed computation is done as follows:
-\begin{enumerate}
-\item A client requests something to a server.
-\item The server does works according to the request.
-\item The client requests to send data to the server.
-\item The server sends the data to the client and the client gets the data.
-\end{enumerate}
-The server is a stack machine. 
-That is OX data message sent by the client
-are pushed to the stack of the server. 
-If the server gets a OX command message, then the data are
-popped form the stack and they are used as arguments of a function call.
-For example, the asir command
-\verb+ ox_push_cmo(P,1) +
-sends an OX data message
-(OX\_DATA,(CMO\_ZZ,1)) to the server $P$.
-Here,
-OX\_DATA stands for OX\_DATA header and 
-(CMO\_ZZ,1) is a body standing for $1$ expressed in CMO data encoding format.
-
-
-
-
-
+%An OpenXM client admit that its own command sends some OX messages
+%sequentially at once.  
+%
+%For example, the asir command
+%{\tt ox\_execute\_string(P, "Print[x+y]")} sends an OX data message
+%{\tt (OX\_DATA, (CMO\_STRING, "Print[x+y]"))} and an OX command message
+%{\tt (OX\_COMMAND, (SM\_executeStringByLocalParser))} to an OpenXM
+%server.