VenueVNCServer available

[Thomas D. Uram]

The server component of the VenueVNC shared application is now available for download:

http://www.mcs.anl.gov/fl/research/accessgrid/software/releases/2.3/patches/VenueVNCServer.py

This program is all Python code, so works similarly on the three
supported platforms:  Windows, Linux, and OSX.  Platform variations
are given here:

* Windows
- Depends on RealVNC (http://realvnc.com/)
- Looks for server executable in the RealVNC install directory
    (C:\Program Files\RealVNC\VNC4\WinVNC4.exe)
- Only the primary display can be shared
- Uses port 5900 for server

* Linux
- Depends on tightvnc (http://www.tightvnc.com) (other vnc packages
   may also work)
- Looks for server executable in /usr/bin/Xvnc
- Any virtual display can be shared via the '--display' option
- Uses port 5900+displaynumber for server (e.g. 5909 for display number 9)

* OSX
- Depends on OSXvnc (http://www.redstonesoftware.com/osxvnc/OSXvnc.html)
- Looks for server executable in /Applications/OSXvnc.app/OSXvnc-server
- Only the primary display can be shared
- Uses port 5900 for server

Users should note the following with respect to security and VNC:
- VNC is regarded as a security risk
   (refer to http://www.realvnc.com/faq.html#security)
- Firewall holes must be opened to allow access to the VNC server from
   outside your network.  Ports are identified above in the plaform notes.


** Execution

VenueVNCServer.py will typically be executed as follows:

    python VenueVNCServer.py --venueUrl https://someserver:8000/Venues/default

On OSX, the environment settings file must be sourced into your environment
before running VenueVNCServer.py (the file is 
/Applications/AccessGridToolkit.app/Contents/Resources/setupenv.sh).

A complete list of command-line options is available by passing the '-h' option.

Bugs should be filed in the AccessGrid bugzilla database at 
http://bugzilla.mcs.anl.gov/accessgrid .