xAP Hub
The xAP Hub allows multiple applications on the same host to share a common xAP infrastructure - fundamental design constraints in the way TCP/IP works would otherwise prevent more than one xAP application being used at a time on a given host.
All applications that use the developer toolkits provided on this site are automatically "hub aware". Provided that the hub is started before any other xAP enabled application is launched, the applications will automatically discover and connect to the hub.
Instructions
A xAP-Hub is required on any host which runs multiple xAP-enabled applications. It is essential that the hub is started before any xAP enabled application. When subsequent xAP enabled applications are started, they should report successful automatic detection of the hub.
Command Line Options
xap-hub [network interface] [udp port] [debug level]
where:
network interface is the network interface used for sending and receiving xAP messages. On a Linux and Windows PC host these are named eth0, eth1. Under OSX they are named ne0 etc. By default, eth0 is used. On a Windows PC which has multiple adapters installed, even if they are not active, eth0 may not represent the active interface - some experimentation may be required!
udp port is the UDP port xAP broadcasts on. By default xAP uses its officially allocated port, 3639. Using an alternative port can be useful during isolated testing, however. Be aware that the use of ports below 1024 will fail unless the application is run by a user with administrative privileges. The use of ports below 1024 therefore has security implications and is not recommend.
debug level determines the verbosity of the output written to stdout. Verbose output can be useful for debugging unexpected behaviour. By default, the debug level is 0. Increasing levels of detail may be specified, up to a maximum of 4.
Download
xAP Hub Project
Windows executable (requires cygwin dll)
Windows / Linux PC / TiVo / Mac source (requires xAP-lib)
|
