

















              TThhee XXIIMM TTrraannssppoorrtt SSppeecciiffiiccaattiioonn


                        RReevviissiioonn 00..11

                  XX VVeerrssiioonn 1111,, RReelleeaassee 77

                        lliibbXX1111 11..33..33





                      _T_a_k_a_s_h_i _F_u_j_i_w_a_r_a
                      FUJITSU LIMITED





                          _A_B_S_T_R_A_C_T

     This specification describes the transport layer
     interfaces between Xlib and IM Server, which makes
     various channels usable such as X protocol or,
     TCP/IP, DECnet and etc.






































Copyright © 1994 by FUJITSU LIMITED

Permission to use, copy, modify, and distribute this docu‐
mentation for any purpose and without fee is hereby granted,
provided that the above copyright notice and this permission
notice appear in all copies.  Fujitsu makes no representa‐
tions about the suitability for any purpose of the informa‐
tion in this document.  This documentation is provided as is
without express or implied warranty.





Copyright © 1994 X Consortium

Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documenta‐
tion files (the ‘‘Software’’), to deal in the Software with‐
out restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to
whom the Software is furnished to do so, subject to the fol‐
lowing conditions:

The above copyright notice and this permission notice shall
be included in all copies or substantial portions of the
Software.

THE SOFTWARE IS PROVIDED ‘‘AS IS’’, WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PUR‐
POSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE X CONSOR‐
TIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE
OR OTHER DEALINGS IN THE SOFTWARE.

Except as contained in this notice, the name of the X Con‐
sortium shall not be used in advertising or otherwise to
promote the sale, use or other dealings in this Software
without prior written authorization from the X Consortium.














_X _W_i_n_d_o_w _S_y_s_t_e_m is a trademark of The Open Group.

































































11..  IInnttrroodduuccttiioonn

The Xlib XIM implementation is layered into three functions,
a protocol layer, an interface layer and a transport layer.
The purpose of this layering is to make the protocol inde‐
pendent of transport implementation.  Each function of these
layers are:

     _T_h_e _p_r_o_t_o_c_o_l _l_a_y_e_r
          implements overall function of XIM and calls the
          interface layer functions when it needs to commu‐
          nicate to IM Server.

     _T_h_e _i_n_t_e_r_f_a_c_e _l_a_y_e_r
          separates the implementation of the transport
          layer from the protocol layer, in other words, it
          provides implementation independent hook for the
          transport layer functions.

     _T_h_e _t_r_a_n_s_p_o_r_t _l_a_y_e_r
          handles actual data communication with IM Server.
          It is done by a set of several functions named
          transporters.

This specification describes the interface layer and the
transport layer, which makes various communication channels
usable such as X protocol or, TCP/IP, DECnet, STREAM, etc.,
and provides the information needed for adding another new
transport layer.  In addition, sample implementations for
the transporter using the X connection is described in sec‐
tion 4.

22..  IInniittiiaalliizzaattiioonn

22..11..  RReeggiisstteerriinngg ssttrruuccttuurree ttoo iinniittiiaalliizzee

The structure typed as TransportSW contains the list of the
transport layer the specific implementations supports.


typedef struct {
      char *transport_name;
      Bool (*config);
} TransportSW;



_t_r_a_n_s_p_o_r_t___n_a_m_e name of transport(*1)

_c_o_n_f_i_g         initial configuration function

───────────
(*1) Refer to "The Input Method Protocol: Appendix
B"



                              11





XXIIMM TTrraannssppoorrtt SSppeecciiffiiccaattiioonn                     lliibbXX1111 11..33..33


A sample entry for the Xlib supporting transporters is shown
below:


TransportSW _XimTransportRec[] = {
/*   char _*_:
 _*   _t_r_a_n_s_p_o_r_t___n_a_m_e,     Bool _(_*_c_o_n_f_i_g_)_(_)
 */
     ‘‘X’’,              _XimXConf,
     ‘‘tcp’’,            _XimTransConf,
     ‘‘local’’,          _XimTransConf,
     ‘‘decnet’’,         _XimTransConf,
     ‘‘streams’’,        _XimTransConf,
     (char *)NULL,       (Bool (*)())NULL,
};



22..22..  IInniittiiaalliizzaattiioonn ffuunnccttiioonn

The following function will be called once when Xlib config‐
ures the transporter functions.

Bool (*config)(_i_m, _t_r_a_n_s_p_o_r_t___d_a_t_a)
      XIM _i_m;
      char _*_t_r_a_n_s_p_o_r_t___d_a_t_a;


_i_m        Specifies XIM structure address.

_t_r_a_n_s_p_o_r_t___d_a_t_a
          Specifies the data specific to the transporter, in
          IM Server address. (*1)

This function must setup the transporter function pointers.

The actual _c_o_n_f_i_g function will be chosen by IM Server at
the pre‐connection time, matching by the _t_r_a_n_s_p_o_r_t___n_a_m_e
specified in the __XXiimmTTrraannssppoorrttRReecc array; The specific mem‐
bers of XimProto structure listed below must be initialized
so that point they appropriate transporter functions.

If the specified transporter has been configured success‐
fully, this function returns True. There is no Alternative
Entry for config function itself.

The structure XimProto contains the following function
pointers:



───────────
(*1) Refer to "The Input Method Protocol: Appendix
B"



                              22





XXIIMM TTrraannssppoorrtt SSppeecciiffiiccaattiioonn                     lliibbXX1111 11..33..33


     Bool (*connect)();       /* Open connection */
     Bool (*shutdown)();      /* Close connection */
     Bool (*write)();         /* Write data */
     Bool (*read)();          /* Read data */
     Bool (*flush)();         /* Flush data buffer */
     Bool (*register_dispatcher)();/* Register asynchronous data handler */
     Bool (*call_dispatcher)();/* Call dispatcher */

These functions are called when Xlib needs to communicate
the IM Server. These functions must process the appropriate
procedure described below.


33..  TThhee iinntteerrffaaccee//ttrraannssppoorrtt llaayyeerr ffuunnccttiioonnss

Following functions are used for the transport interface.

         Table 3‐1; The Transport Layer Functions.

 ┌───────────────────────┬─────────────────────┬──────────┐
 │  AAlltteerrnnaattiivvee EEnnttrryy    │   XXiimmPPrroottoo mmeemmbbeerr   │ SSeeccttiioonn  │
 │  ((IInntteerrffaaccee LLaayyeerr))    │  ((TTrraannssppoorrtt LLaayyeerr))  │          │
 ├───────────────────────┼─────────────────────┼──────────┤
 │__XXiimmCCoonnnneecctt            │ connect             │   3.1    │
 ├───────────────────────┼─────────────────────┼──────────┤
 │__XXiimmSShhuuttddoowwnn           │ shutdown            │   3.2    │
 ├───────────────────────┼─────────────────────┼──────────┤
 │__XXiimmWWrriittee              │ write               │   3.3    │
 ├───────────────────────┼─────────────────────┼──────────┤
 │__XXiimmRReeaadd               │ read                │   3.4    │
 ├───────────────────────┼─────────────────────┼──────────┤
 │__XXiimmFFlluusshh              │ flush               │   3.5    │
 ├───────────────────────┼─────────────────────┼──────────┤
 │__XXiimmRReeggiisstteerrDDiissppaattcchheerr │ register_dispatcher │   3.6    │
 ├───────────────────────┼─────────────────────┼──────────┤
 │__XXiimmCCaallllDDiissppaattcchheerr     │ call_dispatcher     │   3.7    │
 └───────────────────────┴─────────────────────┴──────────┘

The Protocol layer calls the above functions using the
Alternative Entry in the left column. The transport imple‐
mentation defines XimProto member function in the right col‐
umn. The Alternative Entry is provided so as to make easier
to implement the Protocol Layer.


33..11..  OOppeenniinngg ccoonnnneeccttiioonn

When XXOOppeennIIMM is called, the following function is called to
connect with the IM Server.

Bool (*connect)(_i_m)
      XIM _i_m;





                              33





XXIIMM TTrraannssppoorrtt SSppeecciiffiiccaattiioonn                     lliibbXX1111 11..33..33


_i_m        Specifies XIM structure address.

This function must establishes the connection to the IM
Server. If the connection is established successfully, this
function returns True.  The Alternative Entry for this func‐
tion is:

Bool _XimConnect(_i_m)
      XIM _i_m;


_i_m        Specifies XIM structure address.


33..22..  CClloossiinngg ccoonnnneeccttiioonn

When XXCClloosseeIIMM is called, the following function is called to
disconnect the connection with the IM Server. The Alterna‐
tive Entry for this function is:

Bool (*shutdown)(_i_m)
      XIM _i_m;


_i_m        Specifies XIM structure address.

This function must close connection with the IM Server. If
the connection is closed successfully, this function returns
True. The Alternative Entry for this function is:

Bool _XimShutdown(_i_m)
      XIM _i_m;


_i_m   Specifies XIM structure address.


33..33..  WWrriittiinngg ddaattaa

The following function is called, when Xlib needs to write
data to the IM Server.

Bool (*write)(_i_m, _l_e_n, _d_a_t_a)
      XIM _i_m;
      INT16 _l_e_n;
      XPointer _d_a_t_a;


_i_m        Specifies XIM structure address.

_l_e_n       Specifies the length of writing data.

_d_a_t_a      Specifies the writing data.




                              44





XXIIMM TTrraannssppoorrtt SSppeecciiffiiccaattiioonn                     lliibbXX1111 11..33..33


This function writes the _d_a_t_a to the IM Server, regardless
of the contents.  The number of bytes is passed to _l_e_n. The
writing data is passed to _d_a_t_a. If data is sent success‐
fully, the function returns True. Refer to "The Input Method
Protocol" for the contents of the writing data. The Alterna‐
tive Entry for this function is:

Bool _XimWrite(_i_m, _l_e_n, _d_a_t_a)
      XIM _i_m;
      INT16 _l_e_n;
      XPointer _d_a_t_a;


_i_m        Specifies XIM structure address.

_l_e_n       Specifies the length of writing data.

_d_a_t_a      Specifies the writing data.


33..44..  RReeaaddiinngg ddaattaa

The following function is called when Xlib waits for
response from IM server synchronously.

Bool (*read)(_i_m, _r_e_a_d___b_u_f, _b_u_f___l_e_n, _r_e_t___l_e_n)
      XIM _i_m;
      XPointer _r_e_a_d___b_u_f;
      int _b_u_f___l_e_n;
      int _*_r_e_t___l_e_n;


_i_m        Specifies XIM structure address.

_r_e_a_d___b_u_f  Specifies the buffer to store data.

_b_u_f___l_e_n   Specifies the size of the _b_u_f_f_e_r

_r_e_t___l_e_n   Specifies the length of stored data.

This function stores the read data in _r_e_a_d___b_u_f, which size
is specified as _b_u_f___l_e_n. The size of data is set to _r_e_t___l_e_n.
This function return True, if the data is read normally or
reading data is completed.

The Alternative Entry for this function is:











                              55





XXIIMM TTrraannssppoorrtt SSppeecciiffiiccaattiioonn                     lliibbXX1111 11..33..33


Bool _XimRead(_i_m, _r_e_t___l_e_n, _b_u_f, _b_u_f___l_e_n, _p_r_e_d_i_c_a_t_e, _p_r_e_d_i_c_a_t_e___a_r_g)
      XIM _i_m;
      INT16 _*_r_e_t___l_e_n;
      XPointer _b_u_f;
      int _b_u_f___l_e_n;
      Bool _(_*_p_r_e_d_i_c_a_t_e_)_(_);
      XPointer _p_r_e_d_i_c_a_t_e___a_r_g;


_i_m        Specifies XIM structure address.

_r_e_t___l_e_n   Specifies the size of the _d_a_t_a buffer.

_b_u_f       Specifies the buffer to store data.

_b_u_f___l_e_n   Specifies the length of _b_u_f_f_e_r.

_p_r_e_d_i_c_a_t_e Specifies the predicate for the XIM data.

_p_r_e_d_i_c_a_t_e___a_r_g
          Specifies the predicate specific data.

The predicate procedure indicates whether the _d_a_t_a is for
the XIM or not. _l_e_n This function stores the read data in
_b_u_f, which size is specified as _b_u_f___l_e_n. The size of data is
set to _r_e_t___l_e_n.  If _p_r_e_e_d_i_c_a_t_e_(_) returns True, this function
returns True.  If not, it calls the registered callback
function.

The procedure and its arguments are:


Bool (*predicate)(_i_m, _l_e_n, _d_a_t_a, _p_r_e_d_i_c_a_t_e___a_r_g)
      XIM _i_m;
      INT16 _l_e_n;
      XPointer _d_a_t_a;
      XPointer _p_r_e_d_i_c_a_t_e___a_r_g;


_i_m        Specifies XIM structure address.

_l_e_n       Specifies the size of the _d_a_t_a buffer.

_d_a_t_a      Specifies the buffer to store data.

_p_r_e_d_i_c_a_t_e___a_r_g
          Specifies the predicate specific data.


33..55..  FFlluusshhiinngg bbuuffffeerr

The following function is called when Xlib needs to flush
the data.




                              66





XXIIMM TTrraannssppoorrtt SSppeecciiffiiccaattiioonn                     lliibbXX1111 11..33..33


void (*flush)(_i_m)
      XIM _i_m;


_i_m        Specifies XIM structure address.

This function must flush the data stored in internal buffer
on the transport layer. If data transfer is completed, the
function returns True.  The Alternative Entry for this func‐
tion is:

void _XimFlush(_i_m)
      XIM _i_m;


_i_m        Specifies XIM structure address.


33..66..  RReeggiisstteerriinngg aassyynncchhrroonnoouuss ddaattaa hhaannddlleerr

Xlib needs to handle asynchronous response from IM Server.
This is because some of the XIM data occur asynchronously to
X events.

Those data will be handled in the _F_i_l_t_e_r, and the _F_i_l_t_e_r
will call asynchronous data handler in the protocol layer.
Then it calls dispatchers in the transport layer. The dis‐
patchers are implemented by the protocol layer. This func‐
tion must store the information and prepare for later call
of the dispatchers using __XXiimmCCaallllDDiissppaattcchheerr.

When multiple dispatchers are registered, they will be
called sequentially in order of registration, on arrival of
asynchronous data. The register_dispatcher is declared as
following:

Bool (*register_dispatcher)(_i_m, _d_i_s_p_a_t_c_h_e_r, _c_a_l_l___d_a_t_a)
      XIM _i_m;
      Bool _(_*_d_i_s_p_a_t_c_h_e_r_)_(_);
      XPointer _c_a_l_l___d_a_t_a;


_i_m        Specifies XIM structure address.

_d_i_s_p_a_t_c_h_e_r
          Specifies the dispatcher function to register.

_c_a_l_l___d_a_t_a Specifies a parameter for the _d_i_s_p_a_t_c_h_e_r.

The dispatcher is a function of the following type:







                              77





XXIIMM TTrraannssppoorrtt SSppeecciiffiiccaattiioonn                     lliibbXX1111 11..33..33


Bool (*dispatcher)(_i_m, _l_e_n, _d_a_t_a, _c_a_l_l___d_a_t_a)
      XIM _i_m;
      INT16 _l_e_n;
      XPointer _d_a_t_a;
      XPointer _c_a_l_l___d_a_t_a;


_i_m        Specifies XIM structure address.

_l_e_n       Specifies the size of the _d_a_t_a buffer.

_d_a_t_a      Specifies the buffer to store data.

_c_a_l_l___d_a_t_a Specifies a parameter passed to the register_dis‐
          patcher.

The dispatcher is provided by the protocol layer. They are
called once for every asynchronous data, in order of regis‐
tration. If the data is used, it must return True. other‐
wise, it must return False.

If the dispatcher function returns True, the Transport Layer
assume that the data has been processed by the upper layer.
The Alternative Entry for this function is:

Bool _XimRegisterDispatcher(_i_m, _d_i_s_p_a_t_c_h_e_r, _c_a_l_l___d_a_t_a)
      XIM _i_m;
      Bool _(_*_d_i_s_p_a_t_c_h_e_r_)_(_);
      XPointer _c_a_l_l___d_a_t_a;


_i_m        Specifies XIM structure address.

_d_i_s_p_a_t_c_h_e_r
          Specifies the dispatcher function to register.

_c_a_l_l___d_a_t_a Specifies a parameter for the _d_i_s_p_a_t_c_h_e_r.


33..77..  CCaalllliinngg ddiissppaattcchheerr

The following function is used to call the registered dis‐
patcher function, when the asynchronous response from IM
Server has arrived.

Bool (*call_dispatcher)(_i_m, _l_e_n, _d_a_t_a)
      XIM _i_m;
      INT16 _l_e_n;
      XPointer _d_a_t_a;


_i_m        Specifies XIM structure address.





                              88





XXIIMM TTrraannssppoorrtt SSppeecciiffiiccaattiioonn                     lliibbXX1111 11..33..33


_l_e_n       Specifies the size of _d_a_t_a buffer.

_d_a_t_a      Specifies the buffer to store data.

The call_dispatcher must call the dispatcher function, in
order of their registration. _l_e_n and _d_a_t_a are the data
passed to register_dispatcher.

The return values are checked at each invocation, and if it
finds True, it immediately return with true for its return
value.

It is depend on the upper layer whether the read data is XIM
Protocol packet unit or not.  The Alternative Entry for this
function is:

Bool _XimCallDispatcher(_i_m, _l_e_n, _d_a_t_a)
      XIM _i_m;
      INT16 _l_e_n;
      XPointer _c_a_l_l___d_a_t_a;





































                              99





XXIIMM TTrraannssppoorrtt SSppeecciiffiiccaattiioonn                     lliibbXX1111 11..33..33


44..  SSaammppllee iimmpplleemmeennttaattiioonnss ffoorr tthhee TTrraannssppoorrtt LLaayyeerr

Sample implementations for the transporter using the X con‐
nection is described here.


44..11..  XX TTrraannssppoorrtt

At the beginning of the X Transport connection for the XIM
transport mechanism, two different windows must be created
either in an Xlib XIM or in an IM Server, with which the
Xlib and the IM Server exchange the XIM transports by using
the ClientMessage events and Window Properties.  In the fol‐
lowing, the window created by the Xlib is referred as the
"client communication window", and on the other hand, the
window created by the IM Server is referred as the "IMS com‐
munication window".


44..11..11..  CCoonnnneeccttiioonn

In order to establish a connection, a communication window
is created.  A ClientMessage in the following event’s format
is sent to the owner window of XIM_SERVER selection, which
the IM Server has created.

Refer to "The Input Method Protocol" for the XIM_SERVER
atom.

    Table 4‐1; The ClientMessage sent to the IMS window.

───────────────────────┬────────────────────────────────────────────────
SSttrruuccttuurree MMeemmbbeerr       │ CCoonntteennttss
───────────────────────┴────────────────────────────────────────────────
int       type         │ ClientMessage
u_long    serial       │ Set by the X Window System
Bool      send_event   │ Set by the X Window System
Display   *display     │ The display to which connects
Window    window       │ IMS Window ID
Atom      message_type │ XInternAtom(display, ‘‘_XIM_XCONNECT’’, False)
int       format       │ 32
long      data.l[0]    │ client communication window ID
long      data.l[1]    │ client‐major‐transport‐version (*1)
long      data.l[2]    │ client‐major‐transport‐version (*1)
───────────────────────┴────────────────────────────────────────────────


In order to establish the connection (to notify the IM
Server communication window), the IM Server sends a
ClientMessage in the following event’s format to the client
communication window.

      Table 4‐2; The ClientMessage sent by IM Server.




                             1100





XXIIMM TTrraannssppoorrtt SSppeecciiffiiccaattiioonn                     lliibbXX1111 11..33..33


───────────────────────┬───────────────────────────────────────────────────────
SSttrruuccttuurree MMeemmbbeerr       │ CCoonntteennttss
───────────────────────┴───────────────────────────────────────────────────────
int       type         │ ClientMessage
u_long    serial       │ Set by the X Window System
Bool      send_event   │ Set by the X Window System
Display   *display     │ The display to which connects
Window    window       │ client communication window ID
Atom      message_type │ XInternAtom(display, ‘‘_XIM_XCONNECT’’, False)
int       format       │ 32
long      data.l[0]    │ IMS communication window ID
long      data.l[1]    │ server‐major‐transport‐version (*1)
long      data.l[2]    │ server‐minor‐transport‐version (*1)
long      data.l[3]    │ dividing size between ClientMessage and Property (*2)
───────────────────────┴───────────────────────────────────────────────────────



(*1) major/minor‐transport‐version
          The read/write method is decided by the combina‐
          tion of major/minor‐transport‐version, as follows:

     Table 4‐3; The read/write method and the major/minor‐transport‐version

   ┌──────────────────┬───────────────────────────────────────┐
   │TTrraannssppoorrtt‐‐vveerrssiioonn │ rreeaadd//wwrriittee                            │
   ├────────┬─────────┼───────────────────────────────────────┤
   │ mmaajjoorr  │  mmiinnoorr  │                                       │
   ├────────┼─────────┼───────────────────────────────────────┤
   │   0    │    0    │ only‐CM & Property‐with‐CM            │
   │        │    1    │ only‐CM & multi‐CM                    │
   │        │    2    │ only‐CM & multi‐CM & Property‐with‐CM │
   ├────────┼─────────┼───────────────────────────────────────┤
   │   1    │    0    │ PropertyNotify                        │
   ├────────┼─────────┼───────────────────────────────────────┤
   │   2    │    0    │ only‐CM & PropertyNotify              │
   │        │    1    │ only‐CM & multi‐CM & PropertyNotify   │
   └────────┴─────────┴───────────────────────────────────────┘



   only‐CM            :   data is sent via a ClientMessage
   multi‐CM           :   data is sent via multiple ClientMessages
   Property‐with‐CM   :   data is written in Property, and its Atom
                          is send via ClientMessage
   PropertyNotify     :   data is written in Property, and its Atom
                          is send via PropertyNotify


     The method to decide major/minor‐transport‐version is
     as follows:






                             1111





XXIIMM TTrraannssppoorrtt SSppeecciiffiiccaattiioonn                     lliibbXX1111 11..33..33


     (1)  The client sends 0 as major/minor‐transport‐ver‐
          sion to the IM Server.  The client must support
          all methods in Table 4‐3.  The client may send
          another number as major/minor‐transport‐version to
          use other method than the above in the future.

     (2)  The IM Server sends its major/minor‐transport‐ver‐
          sion number to the client. The client sends data
          using the method specified by the IM Server.

     (3)  If major/minor‐transport‐version number is not
          available, it is regarded as 0.


(*2) dividing size between ClientMessage and Property
          If data is sent via both of multi‐CM and Property,
          specify the dividing size between ClientMessage
          and Property. The data, which is smaller than this
          size, is sent via multi‐CM (or only‐CM), and the
          data, which is lager than this size, is sent via
          Property.


44..11..22..  rreeaadd//wwrriittee

The data is transferred via either ClientMessage or Window
Property in the X Window System.


44..11..22..11..  FFoorrmmaatt ffoorr tthhee ddaattaa ffrroomm tthhee CClliieenntt ttoo tthhee IIMM
SSeerrvveerr

CClliieennttMMeessssaaggee

     If data is sent via ClientMessage event, the format is
     as follows:

     Table 4‐4; The ClientMessage event’s format (first or middle)

     ───────────────────────┬────────────────────────────────────────────────
     SSttrruuccttuurree MMeemmbbeerr       │ CCoonntteennttss
     ───────────────────────┴────────────────────────────────────────────────
     int       type         │ ClientMessage
     u_long    serial       │ Set by the X Window System
     Bool      send_event   │ Set by the X Window System
     Display   *display     │ The display to which connects
     Window    window       │ IMS communication window ID
     Atom      message_type │ XInternAtom(display, ‘‘_XIM_MOREDATA’’, False)
     int       format       │ 8
     char      data.b[20]   │ (read/write DATA : 20 byte)
     ───────────────────────┴────────────────────────────────────────────────






                             1122





XXIIMM TTrraannssppoorrtt SSppeecciiffiiccaattiioonn                     lliibbXX1111 11..33..33


     Table 4‐5; The ClientMessage event’s format (only or last)

     ───────────────────────┬────────────────────────────────────────────────
     SSttrruuccttuurree MMeemmbbeerr       │ CCoonntteennttss
     ───────────────────────┴────────────────────────────────────────────────
     int       type         │ ClientMessage
     u_long    serial       │ Set by the X Window System
     Bool      send_event   │ Set by the X Window System
     Display   *display     │ The display to which connects
     Window    window       │ IMS communication window ID
     Atom      message_type │ XInternAtom(display, ‘‘_XIM_PROTOCOL’’, False)
     int       format       │ 8
     char      data.b[20]   │ (read/write DATA : MAX 20 byte)  (*1)
     ───────────────────────┴────────────────────────────────────────────────


     (*1) If the data is smaller than 20 byte, all data
          other than available data must be 0.

PPrrooppeerrttyy

     In the case of large data, data will be sent via the
     Window Property for the efficiency.  There are the fol‐
     lowing two methods to notify Property, and transport‐
     version is decided which method is used.


     (1)  The XChangeProperty function is used to store data
          in the client communication window, and Atom of
          the stored data is notified to the IM Server via
          ClientMessage event.

     (2)  The XChangeProperty function is used to store data
          in the client communication window, and Atom of
          the stored data is notified to the IM Server via
          PropertyNotify event.

     The arguments of the XChangeProperty are as follows:

          Table 4‐6; The XChangeProperty event’s format

     ────────────────────┬────────────────────────────────
     AArrgguummeenntt            │ CCoonntteennttss
     ────────────────────┴────────────────────────────────
     Display   *display  │ The display to which connects
     Window    window    │ IMS communication window ID
     Atom      property  │ read/write property Atom (*1)
     Atom      type      │ XA_STRING
     int       format    │ 8
     int       mode      │ PropModeAppend
     u_char    *data     │ read/write DATA
     int       nelements │ length of DATA
     ────────────────────┴────────────────────────────────




                             1133





XXIIMM TTrraannssppoorrtt SSppeecciiffiiccaattiioonn                     lliibbXX1111 11..33..33


     (*1) The read/write property ATOM allocates the follow‐
          ing strings by XXIInntteerrnnAAttoomm.
               ‘‘_clientXXX’’

     The client changes the property with the mode of Prop‐
     ModeAppend and the IM Server will read it with the
     delete mode i.e. (delete = True).

     If Atom is notified via ClientMessage event, the format
     of the ClientMessage is as follows:

     Table 4‐7; The ClientMessage event’s format to send
                        Atom of property

     ───────────────────────┬────────────────────────────────────────────────
     SSttrruuccttuurree MMeemmbbeerr       │ CCoonntteennttss
     ───────────────────────┴────────────────────────────────────────────────
     int       type         │ ClientMessage
     u_long    serial       │ Set by the X Window System
     Bool      send_event   │ Set by the X Window System
     Display   *display     │ The display to which connects
     Window    window       │ IMS communication window ID
     Atom      message_type │ XInternAtom(display, ‘‘_XIM_PROTOCOL’’, False)
     int       format       │ 32
     long      data.l[0]    │ length of read/write property Atom
     long      data.l[1]    │ read/write property Atom
     ───────────────────────┴────────────────────────────────────────────────



44..11..22..22..  FFoorrmmaatt ffoorr tthhee ddaattaa ffrroomm tthhee IIMM SSeerrvveerr ttoo tthhee
CClliieenntt

CClliieennttMMeessssaaggee

     The format of the ClientMessage is as follows:

     Table 4‐8; The ClientMessage event’s format (first or middle)

     ───────────────────────┬────────────────────────────────────────────────
     SSttrruuccttuurree MMeemmbbeerr       │ CCoonntteennttss
     ───────────────────────┴────────────────────────────────────────────────
     int       type         │ ClientMessage
     u_long    serial       │ Set by the X Window System
     Bool      send_event   │ Set by the X Window System
     Display   *display     │ The display to which connects
     Window    window       │ client communication window ID
     Atom      message_type │ XInternAtom(display, ‘‘_XIM_MOREDATA’’, False)
     int       format       │ 8
     char      data.b[20]   │ (read/write DATA : 20 byte)
     ───────────────────────┴────────────────────────────────────────────────






                             1144





XXIIMM TTrraannssppoorrtt SSppeecciiffiiccaattiioonn                     lliibbXX1111 11..33..33


     Table 4‐9; The ClientMessage event’s format (only or last)

     ───────────────────────┬────────────────────────────────────────────────
     SSttrruuccttuurree MMeemmbbeerr       │ CCoonntteennttss
     ───────────────────────┴────────────────────────────────────────────────
     int       type         │ ClientMessage
     u_long    serial       │ Set by the X Window System
     Bool      send_event   │ Set by the X Window System
     Display   *display     │ The display to which connects
     Window    window       │ client communication window ID
     Atom      message_type │ XInternAtom(display, ‘‘_XIM_PROTOCOL’’, False)
     int       format       │ 8
     char      data.b[20]   │ (read/write DATA : MAX 20 byte) (*1)
     ───────────────────────┴────────────────────────────────────────────────



     (*1) If the data size is smaller than 20 bytes, all
          data other than available data must be 0.

PPrrooppeerrttyy

     In the case of large data, data will be sent via the
     Window Property for the efficiency. There are the fol‐
     lowing two methods to notify Property, and transport‐
     version is decided which method is used.


     (1)  The XChangeProperty function is used to store data
          in the IMS communication window, and Atom of the
          property is sent via the ClientMessage event.

     (2)  The XChangeProperty function is used to store data
          in the IMS communication window, and Atom of the
          property is sent via PropertyNotify event.

     The arguments of the XChangeProperty are as follows:

         Table 4‐10; The XChangeProperty event’s format

     ────────────────────┬──────────────────────────────────
     AArrgguummeenntt            │ CCoonntteennttss
     ────────────────────┴──────────────────────────────────
     Display   *display  │ The display which to connects
     Window    window    │ client communication window ID
     Atom      property  │ read/write property Atom (*1)
     Atom      type      │ XA_STRING
     int       format    │ 8
     int       mode      │ PropModeAppend
     u_char    *data     │ read/write DATA
     int       nelements │ length of DATA
     ────────────────────┴──────────────────────────────────





                             1155





XXIIMM TTrraannssppoorrtt SSppeecciiffiiccaattiioonn                     lliibbXX1111 11..33..33


     (*1) The read/write property ATOM allocates some
          strings, which are not allocated by the client, by
          XXIInntteerrnnAAttoomm.

     The IM Server changes the property with the mode of
     PropModeAppend and the client reads it with the delete
     mode, i.e. (delete = True).

     If Atom is notified via ClientMessage event, the format
     of the ClientMessage is as follows:

     Table 4‐11; The ClientMessage event’s format to send
                        Atom of property

     ───────────────────────┬────────────────────────────────────────────────
     SSttrruuccttuurree MMeemmbbeerr       │ CCoonntteennttss
     ───────────────────────┴────────────────────────────────────────────────
     int       type         │ ClientMessage
     u_long    serial       │ Set by the X Window System
     Bool      send_event   │ Set by the X Window System
     Display   *display     │ The display to which connects
     Window    window       │ client communication window ID
     Atom      message_type │ XInternAtom(display, ‘‘_XIM_PROTOCOL’’, False)
     int       format       │ 32
     long      data.l[0]    │ length of read/write property ATOM
     long      data.l[1]    │ read/write property ATOM
     ───────────────────────┴────────────────────────────────────────────────



44..11..33..  CClloossiinngg CCoonnnneeccttiioonn

If the client disconnect with the IM Server, shutdown func‐
tion should free the communication window properties and
etc..


55..  RReeffeerreenncceess

[1] Masahiko Narita and Hideki Hiura, _‘_‘_T_h_e _I_n_p_u_t _M_e_t_h_o_d
_P_r_o_t_o_c_o_l_’_’
















                             1166


