===================================================================
RCS file: /home/cvs/OpenXM/doc/OpenXM-specs/start-session.tex,v
retrieving revision 1.3
retrieving revision 1.8
diff -u -p -r1.3 -r1.8
--- OpenXM/doc/OpenXM-specs/start-session.tex	2000/01/24 02:48:24	1.3
+++ OpenXM/doc/OpenXM-specs/start-session.tex	2005/03/04 03:49:47	1.8
@@ -1,4 +1,4 @@
-%% $OpenXM: OpenXM/doc/OpenXM-specs/start-session.tex,v 1.2 2000/01/23 00:41:08 noro Exp $
+%% $OpenXM: OpenXM/doc/OpenXM-specs/start-session.tex,v 1.7 2002/01/20 09:26:22 takayama Exp $
 //&jp \section{TCP/IP でのセッションのスタート}
 //&eg \section{How to start a session on TCP/IP}
 
@@ -69,8 +69,8 @@ acts as a control server and controls the server proce
 itself.
 */
 
-//&jp \subsection{byte order の決定}
-//&eg \subsection{Negotiation of the byte order}
+//&jp \subsection{byte order の決定} \label{subsection:byteorder}
+//&eg \subsection{Negotiation of the byte order} \label{subsection:byteorder}
 /*&jp
 コントロールプロセス, 計算プロセス
 ともに, 起動直後に
@@ -96,9 +96,16 @@ Network byte order しか実装していないシステムでは,
 {\tt 0} をおくればよい.
 ただし効率が問題となる通信において, network byte order への変換は
 おおきなボトルネックとなることがあることを了解しておくべきである.
+
+64 bit machine double および 128 bit machine double (浮動小数点数)
+のやりとりに際しても,
+上と同様な方法をもちいるものとする.
+すなわち {\tt double64 *} を {\tt int32 *} にキャストしてから,
+中身を {\tt int32} と同様の処理方法で送受信する.
+例については {\tt CMO\_64BIT\_MACHINE\_DOUBLE}  を見よ.
 */
 /*&eg
-A client and a server exchanges one byte data soon after
+A client and a server exchange one byte data soon after
 the communication has started as follows.
 
 \begin{itemize}
@@ -121,6 +128,13 @@ If a system implements only the network byte order, th
 it is sufficient to send always {\tt 0}.
 However unnecessary byte order conversion may add large overhead
 and it is often a bottle-neck on fast networks.
+
+In order to send and receive 64 bit machine double (floating point number)
+and 128 bit machine double,
+we use the same byte order.
+In other words, we cast {\tt double64 *} to {\tt int32 *} and
+send the array of 4 bytes by the same method with sending {\tt int32}.
+As to examples, see the section on {\tt CMO\_64BIT\_MACHINE\_DOUBLE}. 
 */
 
 \begin{verbatim}
@@ -164,12 +178,12 @@ One time パスワードを安全に配送し, リモートマシンの {\
 */
 /*&eg
 \noindent
-Remark: {\tt ox}, included in {\tt OpenXM/src/kxx}, 
+{\tt ox}, included in {\tt OpenXM/src/kxx}, 
 is a launcher to invoke an engine. After invoking an
 engine, it acts as a control server. By default {\tt ox} requires
 a one time password. To skip it, use {\tt -insecure} option.
 A one time password is a null-terminated byte sequence and
-a client informs the both a control server and an engine of
+a client informs both a control server and an engine of
 byte sequences as one time passwords.
 
 {\tt ox} is created from {\tt oxmain.c} and {\tt
@@ -218,3 +232,14 @@ Byte order for engine process is network byte order.
 \end{verbatim}
 }
 
+//&jp \subsection{OX サーバの利用例}
+//&eg \subsection{Example of using OX servers}
+
+/*&jp
+ox サーバを TCP/IP で $C$ より利用する例は 
+{\tt OpenXM/doc/oxlib/test1-tcp.c} にある.
+*/
+/*&eg
+An sample C source code to use ox servers by TCP/IP can be found
+in {\tt OpenXM/doc/oxlib/test1-tcp.c}.
+*/