What it does...
 Http server with built in cache - allows template driven rendering of html pages, irrespective of when the last xAP update occurred. Http server is a very basic, and nowhere no-where near standards compliant. Do not use this in an insecure environment (e.g. directly connected to the internet) - put a reverse proxy in the way, if you must.
Feed the cache with a page with embedded tags such as <xAP cid:line1:call.text> and the last received caller id data will be substituted for the tag.
The web server also allows simple xAP command execution - if a URL with the extension .xap is requested, the web server generates a local xAP message based on the contents of the requested document. This can be used to provide a simple web interface to any xAP component (e.g. to turn lights off).
Command Line Options
xap-httpcache <http ip address> <http port> <http doc dir> [instance name] [network interface] [udp port] [debug level]
where:
http ip address is the mandatory ip address (not host name) on which to serve web and wap pages. If the server is only required to serve pages on the local machine, it is permissible to bind to the loopback address 127.0.0.1.
http port is the mandatory port number on which to serve web and wap pages. By default most web browsers use port 80. You are free to use another port if port 80 is already in use, however.
http doc dir is the mandatory directory from which the web and web server will serve content.
instance name is the xAP instance name assigned to this web server. By default, the server instance name is Home.
network interface is the network interface used for outgoing 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
Web/wap cache source (requires xAP-lib)
Web/wap cache windows executable (requires cygwin dll)
|
