[Pyxida-cvs-commits] Pyxida/web index.html, 1.13, 1.14 release.sh, 1.1, 1.2

[Jonathan L. <le...@us...>]

Update of /cvsroot/pyxida/Pyxida/web
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv15221/web

Modified Files:
	index.html release.sh 
Log Message:
web page updates

Index: index.html
===================================================================
RCS file: /cvsroot/pyxida/Pyxida/web/index.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -d -r1.13 -r1.14
*** index.html	8 Dec 2006 16:52:09 -0000	1.13
--- index.html	20 Dec 2006 16:42:39 -0000	1.14
***************
*** 145,150 ****
  
  	<p>
! 	Pyxida can be used in two ways: as a "standalone" application
! 	and as a library that you build into your distributed application.
  
  	<p>
--- 145,153 ----
  
  	<p>
! 	Pyxida can be used in three ways: as a "standalone" application,
! 	as a library that you build into your distributed application,
! 	and as a service you query.  The standalone application and
! 	the library are independent software artifacts; the service is
! 	an instance of the library running on PlanetLab.
  
  	<p>
***************
*** 162,165 ****
--- 165,204 ----
  	to help them incorporate the library into their application.
  
+ 	<p><b>For users of the PlanetLab Service:</b></p>
+ 	Pyxida users who just want to query sets of network
+ 	coordinates from an existing system can access our
+ 	long-running PlanetLab Service using XML/RPC.  While you can
+ 	build your own XML/RPC tool, 
+ 	<a href="bin/query.pl">we provide one in perl for you to
+ 	download and use</a>.  Note that this tool require the
+ 	Frontier::Client library to do its network communication; you
+ 	can install this library using CPAN.
+ 
+ 	<p>
+ 	The query tool can: (a) ask a node for its current coordinate,
+ 	(b) ask a node for another node's coordinate, (c) ask for the
+ 	estimated latency between two nodes.  You can find specifics
+ 	on running the tool by running it with no arguments
+ 	(<code>./query.pl</code>).
+ 
+ 	Support for proxy coordinates will be added to the tool in the
+ 	future.  In addition, we are creating a separate tool to
+ 	support the creation and deletion of proxy coordinates.
+ 
+ 	<p>
+ 	Example of querying a node for its own coordinate:<BR>
+ 	query: <code>query.pl -l http://righthand.eecs.harvard.edu:55501</code><BR>
+         response: <code>[493.425 21.099 508.916 -200.796 h0.582]</code>
+ 	</code>
+ 
+ 	<p>
+ 	Example of estimating inter-node latency:<BR>
+ 	query: <code>query.pl -a planetlab01.cs.washington.edu:55504 -b planetlab1.csail.mit.edu:55504 http://righthand.eecs.harvard.edu:55501</code><BR>
+         response: <code>178.520</code>
+ 	</code>
+ 
+ 	<p>Note that we will be changing the path used to access the
+ 	service relatively soon.
+ 
          <p><b>For users of the standalone version:</b></p>
  	<ul>
***************
*** 203,206 ****
--- 242,246 ----
  	create a coordinate for a non-overlay node.</li>
  	<li>add application-level coordinates for improved stability
+ 	<li>version of the library written in Python.
  	</ul>
  

Index: release.sh
===================================================================
RCS file: /cvsroot/pyxida/Pyxida/web/release.sh,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** release.sh	1 Dec 2006 16:48:19 -0000	1.1
--- release.sh	20 Dec 2006 16:42:39 -0000	1.2
***************
*** 4,7 ****
--- 4,12 ----
  cp ../dist/* dist
  
+ echo "Copy bin"
+ cp ../bin/*.pl bin
+ cp ../bin/*.pm bin
+ chmod 664 bin/*
+ 
  echo "Generate Javadoc"
  javadoc -d javadoc/ `find ../src -name "*.java"`