<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body>
If you want to run a venue server, you can execute VenueServer.py. By default,
it will run on hostname:8000. To access this server from outside your firewall,
you need to open ports 8000, 8002, 8004, and 8006. The venue server will
create a single venue at startup. The venue server can be configured using
VenueManagement.py, pointed at the server url (<a class="moz-txt-link-freetext" href="https://hostname:8000/VenueServer">https://hostname:8000/VenueServer</a>).<br>
<br>
We are working on user guide materials now, so a better reference is on its
way.<br>
<br>
Tom<br>
<br>
<br>
Randy Heiland wrote:<br>
<blockquote type="cite"
cite="mid1030424094626.ZM10884@pecos.ncsa.uiuc.edu">
<blockquote type="cite">
<pre wrap="">This problem is a version mismatch between the venue server and venue
client. The venue client code you have is expecting clients and
services in the venue state, but the server to which you are connecting
(presumably vv2:9000) is running beta3 code which does not include
these in the venue state. If you run a client and server from the same
version of the code (both from beta3, say), they would be using the same
definition of venue state, and this problem wouldn't occur. You could
do the same using cvs code, but then there are fewer guarantees.
</pre>
</blockquote>
<pre wrap=""><!---->
Relate to this... is there a doc explaining how one starts up a venue server?
I assume it involves the VenueServer and VenueServerRegistry classes (duh),
but other than that I'm lost.
thanks,
Randy
</pre>
</blockquote>
<br>
</body>
</html>