xpachanges(7) [debian man page]

xpachanges(7)							SAORD Documentation						     xpachanges(7)

NAME

       XPAChanges - Changes For Users from XPA 1.0 and 2.0

SYNOPSIS

       This document describes changes that will affect users who migrate from XPA 1.0 to XPA 2.0.

DESCRIPTION

       There have been a few changes that affect users who upgrade XPA from version 1.0 to version 2.0.  These changes are detailed below.

       o   XPA commands no longer have a resolver routine (this is open to negotiations, but we decided the idea was dumb).  For the SAOtng pro-
	   gram, this means that you must explicitly specify the access point, i.e.,:

	     cat foo.fits | xpaset SAOtng fits

	   instead of:

	     cat foo.fits | xpaset SAOtng

       o   By default, xpaset, xpaget, etc. now wait for the server callback to complete; i.e., the old -W is implied (and the switch is
	   ignored).  This allows support for better error handling.  If you want xpaset, etc.	to return before the callback is complete, use -n
	   switch:

	     echo "file foo.fits" | xpaset -n SAOtng

       o   The old -w switch in xpaset and xpaget is no longer necessary (and is ignored), since you can have more than one process communicating
	   with an xpa access point at one time.

       o   The new -p switch on xpaset means you need not read from stdout:

	     xpaset -p SAOtng colormap I8

	   will send the paramlist to the SAOtng callback without reading from stdin.

SEE ALSO

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

version 2.1.14							   June 7, 2012 						     xpachanges(7)

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)