|
|
tt_spec_write(3) -- write the spec and any associated properties to the ToolTalk database
|
|
The tt_spec_write function writes the spec and any associated properties to the ToolTalk database. The type must be set before the spec is written for the first time. The objid argument is the identifier of the object involved in this operation. |
|
tt_status_message(3) -- provide a message for a problem status code
|
|
The tt_status_message function returns a pointer to a message that describes the problem indicated by this status code. The ttrc argument is the status code received during an operation. |
|
tt_thread_procid(3) -- identify the default process for the currently active thread
|
|
The tt_thread_procid function returns the current default procid for the currently-active thread. If there is no default procid set for the thread, then the process default procid is returned. |
|
tt_thread_procid_set(3) -- set the default procid for the currently active thread
|
|
The tt_thread_procid_set function sets the default procid for the currently active thread. The default procid is an implicit argument to most ToolTalk API calls. |
|
tt_thread_session(3) -- retrieve the default session identifier for the currently active thread
|
|
The tt_thread_session function retrieves the default session identifier for the currently active thread. If there is no default session set for the currently-active thread, then the process default session identifier is returned. A session can have more than one session identifier. This means, for example, that the application cannot compare the result of tt_thread_session with the result of tt_me... |
|
tt_thread_session_set(3) -- set the default session identifier for the current thread
|
|
The tt_thread_session_set function sets the default session identifier for the currently active thread. The ToolTalk service uses the initial user session as the default session and supports one session per procid. The application can make this call before it calls tt_open to specify which session it wants to connect to in the active thread. To change to another opened session, the application mus... |
|
tt_trace_control(3) -- control client-side tracing
|
|
The tt_trace_control function sets or clears an internal flag controlling all client-side tracing. The intent of this is to be called from debugger breakpoints, allowing a programmer to narrow the trace to the suspect area. The value of the onoff argument affects tracing as follows: 0 Tracing is turned off. 1 Tracing is turned on. -1 Tracing is turned on if it was off and vice-versa. |
|
tt_xcontext_join(3) -- add an XDR-interpreted byte-array to the list of values
|
|
The tt_xcontext_join function adds the given XDR-interpreted bytearray value to the list of values for the named contexts of all patterns. The slotname argument describes the slotname in this message. The xdr_proc argument points to the XDR procedure to be used to serialize the data pointed to by value. The value argument is the data to be serialized. |
|
tt_xcontext_quit(3) -- remove an XDR-interpreted byte-array value from the list of values
|
|
The tt_xcontext_quit function removes the given XDR-interpreted bytearray value from the list of values for the contexts of all patterns. The slotname argument describes the slotname in this message. The xdr_proc argument points to the XDR procedure to be used to serialize the data pointed to by value. The value argument is the data to be serialized. |
|
tt_X_session(3) -- return the session associated with an X window system display
|
|
The tt_X_session function returns the session associated with the named X window system display. The application can call tt_X_session before it calls tt_open(3). The xdisplaystring argument is the name of an X display server; for example, somehost:0 or :0. |
|
t_accept(3) -- accept a connect request
|
|
The t_accept() function is issued by a transport user to accept a connect request. fd identifies the local transport endpoint where the connect indication arrived. resfd specifies the local transport endpoint where the connection is to be established. call contains information required by the transport provider to complete the connection. The parameter call points to a t_call structure which conta... |
|
t_alloc(3) -- allocate a library structure
|
|
The t_alloc() function dynamically allocates memory for the various transport function argument structures as specified below. This function will allocate memory for the specified structure and will also allocate memory for buffers referenced by the structure. The structure to allocate is specified by struct_type and must be one of the following: T_BIND struct t_bind T_CALL struct t_call T_OPTMGMT... |
|
t_bind(3) -- bind an address to a transport endpoint
|
|
The t_bind() function associates a protocol address with the transport endpoint specified by fd and activates that transport endpoint. In connection mode, the transport provider may begin enqueuing incoming connect indications or servicing a connection request on the transport endpoint. In connectionless mode, the transport user may send or receive data units through the transport endpoint. The re... |
