BridgeServer instructions

[Thomas D. Uram]

Hi Mike:

Here's are instructions on running a bridge server.  The usage output 
looks like this:

    Usage: BridgeServer.py <<--venueServer venueServerUrl>|
                            <--venueServerFile venueServerFile>|
                            <--file venueUrlFile>|
                            <--venue venueUrl>>
                           <--qbexec quickbridgeExecutable>
                           [--cert certpath]
                           [--key keypath]
                           [--name name]
                           [--location location]
                           [-h|--help]
                           [-d|--debug]

So the required parameters are the path to a QuickBridge executable, and 
one of either a venue server url, a venue server file, a venue url, or a 
venue file.  If given a venue server url, all venues on that server are 
bridged.  If given a venue url, that venue is bridged.  The file options 
provide a mechanism for bridging multiple venue servers or multiple 
venues; in both cases, the file contains a list of urls.

The name and location parameters represent the bridge provider to bridge 
users, in their venue client.  When a user selects "Use Unicast" in the 
venue client, a list of bridges is displayed (by name and location).  
The user selects one and the media tools connect to the bridge addresses.

So here's an example:

python2 BridgeServer.py --qbexec /usr/bin/QuickBridge \
                        --venueServer https://ag21server:8000/VenueServer

I think your use will look more like running a bridge server against 
multiple venue servers, so you'll use the --venueServerFile option instead.

Let me know if you have questions.

Cheers,

Tom






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/ag-dev/attachments/20030820/daac48c7/attachment.htm>