1xpachanges(1)                 SAORD Documentation                xpachanges(1)
2
3
4

NAME

6       XPA Changes: Changes For Users from XPA 1.0 and 2.0
7

SYNOPSIS

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

DESCRIPTION

13       There have been a few changes that affect users who upgrade XPA from
14       version 1.0 to version 2.0.  These changes are detailed below.
15
16       ·   XPA commands no longer have a resolver routine (this is open to
17           negotiations, but we decided the idea was dumb).  For the SAOtng
18           program, this means that you must explicitly specify the access
19           point, i.e.,:
20
21             cat foo.fits ⎪ xpaset SAOtng fits
22
23           instead of:
24
25             cat foo.fits ⎪ xpaset SAOtng
26
27       ·   By default, xpaset, xpaget, etc. now wait for the server callback
28           to complete; i.e., the old -W is implied (and the switch is
29           ignored).  This allows support for better error handling.  If you
30           want xpaset, etc.  to return before the callback is complete, use
31           -n switch:
32
33             echo "file foo.fits" ⎪ xpaset -n SAOtng
34
35       ·   The old -w switch in xpaset and xpaget is no longer necessary (and
36           is ignored), since you can have more than one process communicating
37           with an xpa access point at one time.
38
39       ·   The new -p switch on xpaset means you need not read from stdout:
40
41             xpaset -p SAOtng colormap I8
42
43           will send the paramlist to the SAOtng callback without reading from
44           stdin.
45

SEE ALSO

47       See xpa(n) for a list of XPA help pages
48
49
50
51version 2.1.8                  November 1, 2007                  xpachanges(1)
Impressum