xpaset(1) [debian man page]

xpaset(1)							SAORD Documentation							 xpaset(1)

NAME

       xpaset -  send data to one or more XPA servers

SYNOPSIS

       <data> | xpaset	[-h] [-i nsinet] [-m method] [-n] [-p] [-s] [-t sval,lval] [-u users] [-v] <template|host:port> [paramlist]

OPTIONS

	 -h	       print help message
	 -i	       access XPA point on different machine (override XPA_NSINET)
	 -m	       override XPA_METHOD environment variable
	 -n	       don't wait for the status message after server completes
	 -p	       don't read (or send) buf data from stdin
	 -s	       enter server mode
	 -t [s,l]      set short and long timeouts (override XPA_[SHORT,LONG]_TIMEOUT)
	 -u [users]    XPA points can be from specified users (override XPA_NSUSERS)
	 -v	       verify message to stdout
	 --version     display version and exit

DESCRIPTION

       Data read from stdin will be sent to access points matching the template or host:port.  A set of qualifying parameters can be appended.

       Normally, xpaset reads data input from stdin until EOF and sends those data to the XPA target, along with parameters entered on the command
       line. For example to send a FITS file to the ds9 image display:

	 cat foo.fits | xpaset ds9 fits

       Sometimes, however, it is desirable to send only parameters to an XPA access point, without sending data. For such cases, use the -p
       switch to indicate that there is no data being send to stdin. For example, to change the colormap used by the ds9 image display program,
       use:

	 csh> xpaset -p ds9 cmap Heat

       Of course, this also can be accomplished by sending EOF to stdin in any of the usual ways:

	 csh> echo "" | xpaset ds9 cmap Heat
	 csh> xpaget ds9 cmap Heat < /dev/null
	 csh> xpaset ds9 cmap Heat
	 ^D		       # Ctl-D signals EOF

       The -s switch puts xpaset into server mode, in which commands and data can be sent to access points without having to run xpaset multiple
       times.  (Its not clear if this buys you much!) The syntax for sending commands in server mode is:

	 csh> xpaset -s
	 xpaset ds9 colormap I8
	 ^D
	 xpaset ds9 regions
	 circle 200 300 40
	 circle 300 400 50
	 ^D
       etc.

       After the  required "xpaset" command is specified, optional ASCII data can be appended (as in the region example).  A single data/command
       set is delimited by ^D. Note that typing ^D when a command is expected terminates the program.

       NB: server mode only works from the terminal and only ASCII data can be sent in this way.

       Examples -

	 csh> xpaset ds9 file < foo.fits
	 csh> echo "stop" | xpaset myhost:12345

SEE ALSO

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

version 2.1.14							   June 7, 2012 							 xpaset(1)

Check Out this Related Man Page

xpacmdnew(3)							SAORD Documentation						      xpacmdnew(3)

NAME

       XPACmdNew -  create a new XPA public access point for commands

SYNOPSIS

	 #include <xpa.h>

	 XPA XPACmdNew(char *class, char *name);

DESCRIPTION

       Create a new XPA public access point for commands that will share a common identifier class:name. Enter this access point into the XPA name
       server, so that it can be accessed by external processes.  XPACmdNew() returns an XPA struct.

       It often is more convenient to have one public access point that can manage a number of commands, rather than having individual access
       points for each command. For example, it is easier to command the ds9 image display using:

	 echo "colormap I8"   | xpaset ds9
	 echo "scale log"     | xpaset ds9
	 echo "file foo.fits" | xpaset ds9

       then to use:

	 echo "I8"	 | xpaset ds9_colormap
	 echo "log"	 | xpaset ds9_scale
	 echo "foo.fits" | xpaset ds9_file

       In the first case, the commands remain the same regardless of the target XPA name.  In the second case, the command names must change for
       each instance of ds9.  That is, if a second instance of ds9 called DS9 were running, it would be commanded either as:

	 echo "colormap I8"   | xpaset DS9
	 echo "scale log"     | xpaset DS9
	 echo "file foo.fits" | xpaset DS9

       or as:

	 echo "I8"	 | xpaset DS9_colormap
	 echo "log"	 | xpaset DS9_scale
	 echo "foo.fits" | xpaset DS9_file

       Thus, in cases where a program is going to manage many commands, it generally is easier to define them as commands associated with the
       XPACmdNew() routine, rather than as separate access points using XPANew().

       When XPACmdNew() is called, only the class:name identifier is specified.  Each sub-command is subsequently defined using the XPACmdAdd()
       routine.

SEE ALSO

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

version 2.1.14							   June 7, 2012 						      xpacmdnew(3)

Linux and UNIX Man Pages

xpaset(1) [debian man page]

Check Out this Related Man Page