OpenXM/doc/ascm2001p/session-management.tex - diff

Return to session-management.tex CVS log

Up to [local] / OpenXM / doc / ascm2001p

version 1.1, 2001/06/19 07:32:59

version 1.3, 2001/06/21 03:09:46

Line 1

% $OpenXM$

% $OpenXM: OpenXM/doc/ascm2001p/session-management.tex,v 1.2 2001/06/20 05:42:48 takayama Exp $

\section{Session Management}

\label{secsession}

Line 41 computations.

Under OpenXM-RFC 100, servers are invoked as follows.

An application called {\it launcher} is invoked from a client.

The launcher sets up two communication channels: the data channel

and the control. Then it creates a server process which can communicate

and the control channel.

Then it creates a server process which can communicate

with the client via the data channel. Finally the launcher

acts as a control server and controls the server process.

As to the details of the control server see Section \ref{control}.

Line 56 As to the details of the control server see Section \r

Line 57 As to the details of the control server see Section \r

%order. Nevertheless it is necessary to negotiate the byte order to

%skip the byte order conversion because its cost is often dominant over

%fast networks.

OpenXM-RFC 101 \cite{ox-rfc-101} gives more secure and

OpenXM-RFC 101\cite{ox-rfc-101} gives a more secure and

efficient way to start servers.

It uses ``ssh'' to launch a control server and

the control server can launch one or more than one

engines.

See \cite{ox-rfc-101} for details.

\subsection{Control server}

\subsection{Resetting an engine}

\label{control}

%In OpenXM we adopted the following simple and robust method to

%control servers.