home *** CD-ROM | disk | FTP | other *** search
-
-
-
- - 1 -
-
-
-
- 4. _D_i_f_f_e_r_e_n_c_e_s__f_r_o_m__S_u_n_S_o_f_t__T_o_o_l_T_a_l_k
-
- 4.1 _N_o_t__S_u_p_p_o_r_t_e_d__i_n__S_i_l_i_c_o_n__G_r_a_p_h_i_c_s__T_o_o_l_T_a_l_k
-
- +o The Classing Engine is a SunSoft database used for
- typing information (for example, given a file, what
- type is it, what icon is used for this type?). This is
- used in Sun OpenWindows, and is not part of ToolTalk.
- Some of the ToolTalk commands have options that use the
- Classing Engine in the SunSoft implementation. The
- Classing Engine options are not supported in the
- Silicon Graphics (SGI) implementation.
-
- +o The SunSoft implementation of ToolTalk supports a _d_e_s
- authentication option and uses secure RPC. This is not
- supported in the SGI ToolTalk implementation.
-
- +o The SunSoft implementation of ToolTalk supports
- _i_n_t_e_r_n_a_t_i_o_n_a_l_i_z_a_t_i_o_n of error/warning messages. This is
- not supported in the SGI ToolTalk implementation. The
- error message strings can be found in Appendix C of the
- _T_o_o_l_T_a_l_k _P_r_o_g_r_a_m_m_e_r'_s _G_u_i_d_e.
-
- 4.2 _R_e_s_t_r_i_c_t_e_d__S_u_p_p_o_r_t__i_n__S_G_I__T_o_o_l_T_a_l_k
-
- +o The following examples in _t_o_o_l_t_a_l_k__d_e_v._s_w._e_x_a_m_p_l_e_s
- (/_u_s_r/_T_o_o_l_T_a_l_k/_e_x_a_m_p_l_e_s) do _n_o_t run on IRIS
- workstations: _t_t_s_a_m_p_l_e_1, _S_u_n__E_d_i_t_D_e_m_o, _t_t_m_o_n. They are
- included for illustrative purposes only. However, two
- examples have been written to run on IRIS systems,
- _t_t_s_a_m_p_l_e_1__s_g_i and
- _t_t_s_a_m_p_l_e_2__s_g_i__c_l_i_e_n_t/_t_t_s_a_m_p_l_e_2__s_g_i__s_e_r_v_i_c_e. These new
- examples are presented in Chapter 6.
-
- +o The following libraries are needed when binding in
- either the shared or non-shared ToolTalk libraries:
- /_u_s_r/_l_i_b/_l_i_b_c._s_o
- /_u_s_r/_l_i_b/_l_i_b_X_1_1._s_o
-
-
- 4.3 _C_h_a_n_g_e_s__i_n__S_G_I__T_o_o_l_T_a_l_k
-
- +o The SunSoft implementation of ToolTalk has a program
- named _t_t_c_p for copying files containing ToolTalk
- objects. In SGI's implementation, _t_t_c_p is a test
- program for TCP and UDP performance. The SunSoft
- ToolTalk _t_t_c_p command has been renamed _t_t_c_o_p_y in SGI
- ToolTalk.
-
-
-
-
-
-
-
-
-
-
-
-
- - 2 -
-
-
-
- 4.4 _A_d_d_i_t_i_o_n_a_l__F_u_n_c_t_i_o_n_a_l_i_t_y__o_f__S_G_I__T_o_o_l_T_a_l_k
-
- By default, a ToolTalk client process connects to a default
- ToolTalk message server (ttsession). Silicon Graphics has
- modified the default behavior to include the concept of the
- CASEVision/ClearCase _v_i_e_w. By default, if ToolTalk clients
- are running in a CASEVision/ClearCase _v_i_e_w, the ttsession
- will be started in the _v_i_e_w and dedicated only to processes
- in the _v_i_e_w. This overrides the SunSoft ToolTalk default
- mechanism. If the ToolTalk client is not running in a
- CASEVision/ClearCase _v_i_e_w, it connects to the ttsession in
- the same manner as in the SunSoft ToolTalk implementation.
- (See CASEVision/ClearCase for details on what it means to be
- in a _v_i_e_w).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-