OpenXM/doc/calc2000/ox-messages.tex - diff

Return to ox-messages.tex CVS log

Up to [local] / OpenXM / doc / calc2000

version 1.1.1.1, 2000/04/24 04:20:11

version 1.3, 2000/04/26 08:18:31

Line 1

%%$OpenXM: OpenXM/doc/issac2000/ox-messages.tex,v 1.7 2000/01/16 06:02:41 takayama Exp $

%%$OpenXM: OpenXM/doc/calc2000/ox-messages.tex,v 1.2 2000/04/24 05:01:29 noro Exp $

\section{OX messages}

Line 20 are allowed and the byte order is determined as a part

the establishment of a connection. See Section \ref{secsession} for details.

The OX messages are classified into three types:

DATA, COMMAND, and SPECIAL.

COMMAND, DATA and SPECIAL.

We have currently the following general tags for the OX messages.

\begin{verbatim}

\begin{tabbing}

#define OX_COMMAND 513 // COMMAND

AAAAAAAAA \= \kill

#define OX_DATA 514 // DATA

COMMAND \> {\tt OX\_COMMAND}\\

#define OX_SYNC_BALL 515 // SPECIAL

DATA \> {\tt OX\_DATA}, {\tt OX\_DATA\_WITH\_LENGTH}, {\tt OX\_DATA\_OPENMATH\_XML},\\

#define OX_DATA_WITH_LENGTH 521 // DATA

\> {\tt OX\_DATA\_OPENMATH\_BINARY} {\tt OX\_DATA\_MP} \\

#define OX_DATA_OPENMATH_XML 523 // DATA

SPECIAL \> {\tt OX\_SYNC\_BALL}

#define OX_DATA_OPENMATH_BINARY 524 // DATA

\end{tabbing}

#define OX_DATA_MP 525 // DATA

\end{verbatim}

A new OX tag may be added.

The new tag should be classified into DATA or COMMAND.

For example, \verb+ OX_DATA_ASIR_LOCAL_BINARY + was added recently