Page History

PerfSONAR

...

1. Middleware
   1. Document User API for perfSONAR: Asif
      1. how does this differ from perfsonarui?

   2. Wiki Markup

1. 1. Study the perfSONAR NMWG request/response schema \[Done 5/1/07\]: Qasim

...

1. 1. 1. Document

...

1. 1. 1. NMWG

...

1. 1. 1. request/response

...

1. 1. 1. schema

...

1. 1. 1. on

...

1. 1. 1. wiki:

...

1. 1. 1. Qasim

...

1. 2. Output

...

1. 1. from

...

1. 1. some

...

1. 1. script

...

1. 1. (mtml.pm?)

...

1. 1. is

...

1. 1. unintelligible

...

1. 1. (e.g.

...

1. 1. control

...

1. 1. characters)

...

1. 1. need

...

1. 1. help

...

1. 1. from

...

1. 1. Asif,

...

1. 1. Nauman

...

1. 1. will

...

1. 1. send

...

1. 1. snapshot

...

1. 1. o

...

1. 1. Asif

...

1. 1. (5/10/07):

...

1. 1. Nauman

   2. Wiki Markup
      *{-}Execute sample request queries for utilization and metadata from{-}* *-[|http://perfsonar.acad.bg/perfsonar.jnlp]-{*}{*}-[*{-}perfSONARUI{-}*|http://perfsonar.acad.bg/perfsonar.jnlp]-{*}{*}-: Qasim

...

1. 1. \[Done\]-*

   2. Having Java socket error, maybe firewall problem
   3. Add updated code into SVN: Asif
2. Visualisation
   1. Provide 3-dimensional spinny (interactive) globe interface like with mona-lisa in java
      1. integrate into Asif's topoviz frontend: Qasim
      2. integrate into perfsonarUI: TBA
   2. Googlemaps
      1. Download and understand code from internet2 svn
      2. install locally
      3. Investigate google maps API's and extensions to provide 'traffic' like visualisation (look at google maps at the Bay Area for example)
   3. Ping summary table: Nauman
      1. status? (was first thing ever assigned to nauman)