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

Return to ox-messages.tex CVS log

Up to [local] / OpenXM / doc / issac2000

Diff for /OpenXM/doc/issac2000/ox-messages.tex between version 1.2 and 1.6

version 1.2, 2000/01/03 04:27:53

version 1.6, 2000/01/15 12:18:42

Line 1

%%$OpenXM: OpenXM/doc/issac2000/ox-messages.tex,v 1.1 2000/01/02 07:32:12 takayama Exp $

%%$OpenXM: OpenXM/doc/issac2000/ox-messages.tex,v 1.5 2000/01/15 03:46:27 noro 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.

Line 14 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:

The OX messages are classified into three types:

DATA, COMMAND, and others.

DATA, COMMAND, and SPECIAL.

We have the following main tags for the OX messages.

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

Line 34 We have the following main tags for the OX messages.

New OX tags may be added.

The new tag should be classified into DATA or COMMAND.

For example, \verb+ OX_DATA_ASIR_LOCAL_BINARY + was added a few month ago

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 classifed to DATA.

This is a tag classified to DATA.

See the home page of OpenXM to add a new tag.

See the web page of OpenXM to add a new tag \cite{openxm-web}.

Any server is a stack machine (see Section~\ref{sec:ox-stackmachines}

for detail).

{\it OX data} message sent by a client

are pushed onto the stack of a server.

If the server gets an {\it OX command} message, then the server

executes the command.

In OpenXM, a distributed computation is done as follows:

For example, the asir command {\tt ox\_push\_cmo(P,1)}

\begin{enumerate}

(push integer $1$ onto the server $P$)

\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 stackmachine.

That is {\it OX data} message sent by the client

are pushed to the stack of the server.

If the server gets an {\it 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) + (push integer $1$ to the server P)

sends an OX data message

(OX\_DATA,(CMO\_ZZ,1)) to the server $P$.

{\tt (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

{\tt (CMO\_ZZ,1)} is a body standing for $1$ expressed

in the CMO data encoding format.

The server tranlates $(CMO\_ZZ, 1)$ to its own internal object fotrmat

for integers and pushs the object onto the stack.

%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.

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>