xpacmdadd(3) [debian man page]

xpacmdadd(3)							SAORD Documentation						      xpacmdadd(3)

NAME

       XPACmdAdd -  add a command to an XPA command public access point

SYNOPSIS

	 #include <xpa.h>

	 XPACmd XPACmdAdd(XPA xpa, char *name, char *help,
			  int (*send_callback)(),
			  void *send_data, char *send_mode,
			  int (*rec_callback)(),
			  void *rec_data,  char *rec_mode);

DESCRIPTION

       Add a command to an XPA command access point. The XPA argument specifies the XPA struct returned by a call to XPANewCmd(). The name argu-
       ment is the name of the command. The other arguments function identically to the arguments in the XPANew() command, i.e., the send_callback
       and rec_callback routines have identical calling sequences to their XPANew() counterparts, with the exceptions noted below.

       When help is requested for a command access point using:

	 xpaget -h class:name

       all of the command help strings are listed.  To get help for a given command, use:

	 xpaget -h class:name cmd

       Also, the acl keyword in the send_mode and receive_mode strings is global to the access point, not local to the command.  Thus, the value
       for the acl mode should be the same in all send_mode (or receive_mode) strings for each command in a command access point. (The acl for
       send_mode need not be the same as the acl for receive_mode, though).

SEE ALSO

       See xpa(7) for a list of XPA help pages

version 2.1.14							   June 7, 2012 						      xpacmdadd(3)

xpacode(7)							SAORD Documentation							xpacode(7)

NAME

       XPACode -  Where to Find Example/Test Code

SYNOPSIS

       The XPA source code directory contains two test programs, stest.c, and ctest.c that can serve as examples for writing XPA servers and
       clients, respectively.  They also can be used to test various features of XPA.

DESCRIPTION

       To build the XPA test programs, execute:

	  make All

       in the XPA source directory to generate the stest and ctest programs.  (NB: this should work on all platforms, although we have had prob-
       lems with unresolved externals on one Sun/Solaris machine, for reasons still unknown.)

       The stest program can be executed with no arguments to start an XPA server that contains the access points: xpa, xpa1, c_xpa (containing
       sub-commands cmd1 and cmd2), and i_xpa.	You then can use xpaset and xpaget to interact with these access points:

	 cat xpa.c | xpaset xpa      # send to xpa
	 cat xpa.c | xpaset "xpa*"   # send to xpa and xpa1
	 xpaget xpa		     # receive from xpa
	 xpaget xpa*		     # receive from xpa and xpa1

       etc. You also can use ctest to do the same thing, or to iterate:

	 ctest -s -l 100 xpa	    # send to xpa 100 times
	 ctest -s -l 100 "xpa*"     # send to xpa and xpa1 100 times
	 ctest -g -l 100 xpa	    # receive from xpa 100 times
	 ctest -g -l 100 "xpa*"     # receive from xpa and xpa1 100 times

       More options are available: see the stest.c and ctest.c code itself, which were used extensively to debug XPA.

       The file test.tcl in the XPA source directory gives examples for using the XPATclInterface.

SEE ALSO

       See xpa(7) for a list of XPA help pages

version 2.1.14							   June 7, 2012 							xpacode(7)