...
The main puropse of TULIP Central Reflector is to proxy the TULIP quieries queries to PlanetLab's Scriptroute Service. It may also be extended to issue all queriese. the PlanetLab Scriptroute service provides a cookie which works for a single IP address only. So in this way all the requests will be issued from the Central reflector and the responses will be sent back to the TULIP JNLP Client.
Implementation
| Wiki Markup |
|---|
The TULIP Central reflector will be a CGI Script (reflector.cgi) deployed at SLAC. The TULIP client will issue a single request and the Reflector will go ahead and probe all the landmarks in that region*\[1\] and return the results to the TULIP Client. |
...
Requirements
- Should fetch sites.txt or have a local copy of sites.txt ( What , what changes should be made to sites.txt ? Maybe a
- A new parameter
- should be added to sites.txt to include teir0 or teir1. Also the region of tier1 sites needs to be specified in sites.txt
- A seperate separate thread should be used for each landmark and Semaphores should be used for locking, so that data from different threads should not inter-mix.
- There should be a limited limit on the number of threads that can be launched at a time (say 10).Logging should be enabled on the server side
- Should there be extra logging on the reflector or can we rely on the standard web logs which will log each query including time stamp, the client name. What else it logs depends on whether the rewuest is Get or a Post.
- What should happen if a landmark responds with a bad data. ( Should it process the error or send the raw data back?). Since there will be some anomalies I suspect the reflector will need to return the full response and anyhow needs to inform the user, so I suspect initially the clinet will process the response and spot errors etc.)
- Special consideration for security as the script ultimately has to be deployed at SLAC ( Perl taint option, warning oprion, special open method etc)
...