| version 1.8, 2000/11/30 02:41:36 |
version 1.9, 2002/01/20 09:26:22 |
|
|
| %% $OpenXM: OpenXM/doc/OpenXM-specs/control.tex,v 1.7 2000/11/17 02:50:04 takayama Exp $ |
%% $OpenXM: OpenXM/doc/OpenXM-specs/control.tex,v 1.8 2000/11/30 02:41:36 takayama Exp $ |
| \section{Session Management} |
\section{Session Management} |
| |
|
| \subsection{Control server} |
\subsection{Control server} |
| Line 245 OpenXM ¥µ¡¼¥Ð¤Ï, ²Äǽ¤Ç¤¢¤ë¤«¤®¤ê²ÉÌۤǤ¢¤ë. |
|
| Line 245 OpenXM ¥µ¡¼¥Ð¤Ï, ²Äǽ¤Ç¤¢¤ë¤«¤®¤ê²ÉÌۤǤ¢¤ë. |
|
| ¤«¤®¤ê²¿¤âÁ÷¿®¤·¤Ê¤¤. |
¤«¤®¤ê²¿¤âÁ÷¿®¤·¤Ê¤¤. |
| */ |
*/ |
| /*&eg |
/*&eg |
| OpenXM servers try to be quiet as far as possible. |
OpenXM servers try to be as quiet as possible. |
| For example, engine errors of a server are only put on the engine stack and |
For example, engine errors of a server are only put on the engine stack and |
| the engine does not send error packets unless the client sends the message |
the engine does not send error packets unless the client sends the message |
| {\tt pop\_cmo}. |
{\tt pop\_cmo}. |
| Line 259 OpenXM ¤Ï¤³¤Î¸¶Â§¤ò¤ä¤Ö¤ëÎ㳰Ū¤ÊÊýË¡¤ò°ì¤ÄÍÑ°Õ¤·¤Æ¤¤¤ |
|
| Line 259 OpenXM ¤Ï¤³¤Î¸¶Â§¤ò¤ä¤Ö¤ëÎ㳰Ū¤ÊÊýË¡¤ò°ì¤ÄÍÑ°Õ¤·¤Æ¤¤¤ |
|
| ¤³¤Îµ¡Ç½¤Ï mathcap ¤Ç¶Ø»ß¤¹¤ë¤³¤È¤â²Äǽ¤Ç¤¢¤ë. |
¤³¤Îµ¡Ç½¤Ï mathcap ¤Ç¶Ø»ß¤¹¤ë¤³¤È¤â²Äǽ¤Ç¤¢¤ë. |
| */ |
*/ |
| /*&eg |
/*&eg |
| OpenXM provides a method to break this principle. |
OpenXM provides a method to notify events. |
| Control server may send {\tt OX\_NOTIFY} header and an {\tt OX\_DATA} packet. |
Control server may send {\tt OX\_NOTIFY} header and an {\tt OX\_DATA} packet. |
| This transmission can be prohibited by mathcap. |
This transmission may be prohibited by mathcap. |
| */ |
*/ |
| |
|
| /*&jp |
/*&jp |
| Line 274 quit ¥Ü¥¿¥ó¤¬¤ª¤µ¤ì¤ë¤È canvas ¤¬¾ÃÌǤ¹¤ë¤¬, ¥¨¥ó¥¸¥ó¼ |
|
| Line 274 quit ¥Ü¥¿¥ó¤¬¤ª¤µ¤ì¤ë¤È canvas ¤¬¾ÃÌǤ¹¤ë¤¬, ¥¨¥ó¥¸¥ó¼ |
|
| {\tt OX\_NOTIFY} ¤òÍѤ¤¤ë. |
{\tt OX\_NOTIFY} ¤òÍѤ¤¤ë. |
| */ |
*/ |
| /*&eg |
/*&eg |
| Let us explain how to use {\tt OX\_NOTIFY}. |
Let us explain how to use {\tt OX\_NOTIFY} by an example. |
| The {\tt ox\_plot} server of {\tt asir} has a quit button. |
The {\tt ox\_plot} server of {\tt asir} has a quit button. |
| If the quit button is pressed, the canvas dissappears, but the engine |
If the quit button is pressed, the canvas dissappears, but the engine |
| does not terminate. |
does not terminate. |
| Line 290 the {\tt OX\_NOTIFY} message should be used. |
|
| Line 290 the {\tt OX\_NOTIFY} message should be used. |
|
| ¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤è¤¦. |
¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤è¤¦. |
| ¤·¤¿¤¬¤Ã¤Æ¥¨¥ó¥¸¥ó¤Ï¤Ê¤ó¤é¤«¤ÎÊýË¡¤Ç, ¥³¥ó¥È¥í¡¼¥ë¥µ¡¼¥Ð¤Ë |
¤·¤¿¤¬¤Ã¤Æ¥¨¥ó¥¸¥ó¤Ï¤Ê¤ó¤é¤«¤ÎÊýË¡¤Ç, ¥³¥ó¥È¥í¡¼¥ë¥µ¡¼¥Ð¤Ë |
| {\tt OX\_NOTIFY} ¤ò¤ª¤¯¤ë¤³¤È¤ò°ÍÍꤷ¤Ê¤¤¤È¤¤¤±¤Ê¤¤. |
{\tt OX\_NOTIFY} ¤ò¤ª¤¯¤ë¤³¤È¤ò°ÍÍꤷ¤Ê¤¤¤È¤¤¤±¤Ê¤¤. |
| OpenXM ¤Îµ¬³Ê¤Ç¤Ï, |
¤³¤ÎÊýË¡¤Ï, OS ¤Ë¤è¤ê¤¤¤í¤¤¤í¤ÊÊýË¡¤¬²Äǽ¤À¤«, |
| ¥Õ¥¡¥¤¥ë {\tt /tmp/.ox\_notify.pid} ¤Ë touch ¤¹¤ë¤³¤È¤Ç¤³¤ì¤Î |
¤¿¤È¤¨¤Ð, unix ¤Ç¤Ï |
| °ì¤Ä¤Î¼Â¸½ÊýË¡¤òÍ¿¤¨¤Æ¤¤¤ë. |
¥Õ¥¡¥¤¥ë {\tt /tmp/.ox\_notify.pid} ¤Ë touch ¤¹¤ë¤³¤È¤Ç¤³¤ì¤ò |
| |
°ì¤Ä¤Î¼Â¸½¤¹¤ë¤³¤È¤¬²Äǽ¤Ç¤¢¤ë. |
| ¤³¤³¤Ç {\tt pid} ¤Ï¥¨¥ó¥¸¥ó¤Î¥×¥í¥»¥¹ÈÖ¹æ¤Ç¤¢¤ë. |
¤³¤³¤Ç {\tt pid} ¤Ï¥¨¥ó¥¸¥ó¤Î¥×¥í¥»¥¹ÈÖ¹æ¤Ç¤¢¤ë. |
| ¥³¥ó¥È¥í¡¼¥ë¥µ¡¼¥Ð¤Ï¥Õ¥¡¥¤¥ë {\tt /tmp/.ox\_notify.pid} ¤¬ |
¥³¥ó¥È¥í¡¼¥ë¥µ¡¼¥Ð¤Ï¥Õ¥¡¥¤¥ë {\tt /tmp/.ox\_notify.pid} ¤¬ |
| touch ¤µ¤ì¤¿¤³¤È¤ò¸¡½Ð¤·¤¿¤é, ¥¯¥é¥¤¥¢¥ó¥È¤Ë |
touch ¤µ¤ì¤¿¤³¤È¤ò¸¡½Ð¤·¤¿¤é, ¥¯¥é¥¤¥¢¥ó¥È¤Ë |
| Line 301 touch ¤µ¤ì¤¿¤³¤È¤ò¸¡½Ð¤·¤¿¤é, ¥¯¥é¥¤¥¢¥ó¥È¤Ë |
|
| Line 302 touch ¤µ¤ì¤¿¤³¤È¤ò¸¡½Ð¤·¤¿¤é, ¥¯¥é¥¤¥¢¥ó¥È¤Ë |
|
| ¶¦Í¥á¥â¥ê¤ä¥·¥°¥Ê¥ë¤òÍѤ¤¤Æ¤·¤é¤»¤Æ¤â¤è¤¤. |
¶¦Í¥á¥â¥ê¤ä¥·¥°¥Ê¥ë¤òÍѤ¤¤Æ¤·¤é¤»¤Æ¤â¤è¤¤. |
| */ |
*/ |
| /*&eg |
/*&eg |
| Let us note that it is the control process that sends {\tt OX\_NOTIFY}. |
Let us note that only the control process is allowed to send {\tt OX\_NOTIFY}. |
| Therefore, the engine must ask the control server to send |
Therefore, the engine must ask the control server to send |
| {\tt OX\_NOTIFY}. |
{\tt OX\_NOTIFY}. |
| In the OpenXM, if the engine touches the file |
Methods to ask the control process from the engine |
| |
depends on operating system. |
| |
In case of unix, one method is the use of a file; |
| |
for instance, |
| |
if the engine touches the file |
| {\tt /tmp/.ox\_notify.pid}, then the control server sends |
{\tt /tmp/.ox\_notify.pid}, then the control server sends |
| the {\tt OX\_NOTIFY} header and the {\tt OX\_DATA} packet |
the {\tt OX\_NOTIFY} header and the {\tt OX\_DATA} packet |
| of {\tt cmo\_null}. |
of {\tt cmo\_null}. |
| Here, {\tt pid} is the process id of the engine. |
Here, {\tt pid} is the process id of the engine. |
| Engines and control processes may use a shared memory or a signal |
Engines and control processes may use a shared memory or a signal |
| instead of the file {\tt /tmp.ox\_notify.pid}. |
instead of the file {\tt /tmp/.ox\_notify.pid}. |
| */ |
*/ |
![[BACK]](/icons/cvsweb/back.gif){kind=icon}
Return to control.tex CVS log ![[TXT]](/icons/cvsweb/text.gif){kind=icon}
![[DIR]](/icons/cvsweb/dir.gif){kind=icon}
Up to [local] / OpenXM / doc / OpenXM-specs