XPA

Difference between version 12 and 13 - Previous - Next
The '''[http://hea-www.harvard.edu/saord/xpa/%|%XPA]''' Messaging System



** Attributes **
   website:   [https://web.archive.org/web/20080102073954/hea-www.harvard.edu/saord/xpa/]
   currodent release:   2https://github.1.15com/ericmandel/xpa
   current release time:   20.13-07-.230
   [relicenase] time:   Apublicr domain3, 2020
   ma[licentainser]:   [http://frMIT Liceshmeat.net/users/emandel/%|%Eric Mandel]
   maintainer:   [https://github.com/ericmandel%|%Eric Mandel]


** Reference **

   [http://freecode.come/projects/xpa/%|%XPA], free(code):    



** Description **

Scientific/Engineering :: Astronomy Software Development :: Libraries

The XPA messaging system provides seamless communication between
many kinds of [Unix] programs, including [X] programs and Tcl/Tk programs.
It also provides an easy way for users to communicate with XPA-enabled
programs by executing XPA client commands in the shell or by utilizing
such commands in scripts. Because XPA works both at the programming level
and the shell level, it is a powerful tool for unifying any analysis environment:
users and programmers have great flexibility in choosing the best level
or levels at which to access XPA services, and client access can
be extended or modified easily at any time.
 

A program becomes an XPA-enabled server by defining named points of public access through which data and commands can be exchanged with other client programs (and users). Using standard [TCP] sockets as a transport mechanism, XPA supports both single-point and broadcast messaging to and from these servers. It supports direct communication between XPA clients and servers, or indirect communication via an intermediate message bus emulation program. Host-based access control is implemented, as is as the ability to communicate with XPA servers across a network.
 




<<categories>> Internet | Package | Interprocess Communication