Loukik Kudarimoti wrote:
Hello Gang,
It has come to our notice that the messages in v2 responses do not specify units while giving back measurement data (ex: Bandwidth Utilization and Capacity). Specifying such units is necessary and messages should be enhanced to support this.
Also, there is scope for optimization in such specification. For example, while returning back data
instead of
<perfsonar:datum timeValue="1127183580" value="7.620117028888889E7" units ="bps"/> <perfsonar:datum timeValue="1127183640" value="1.4989345286805557E7" units ="bps"/> <perfsonar:datum timeValue="1127183700" value="1.50811390446627E7" units ="bps"/>
we could specify it just once..maybe like this:
<perfsonar:data dataUnits="bps"> <perfsonar:datum timeValue="1127183580" value="7.620117028888889E7"/> <perfsonar:datum timeValue="1127183640" value="1.4989345286805557E7"/> <perfsonar:datum timeValue="1127183700" value="1.50811390446627E7"/> </perfsonar:data>
or like this:
<perfsonar:data> <perfsonar:units dataUnits="bps"/> <perfsonar:datum timeValue="1127183580" value="7.620117028888889E7"/> <perfsonar:datum timeValue="1127183640" value="1.4989345286805557E7"/> <perfsonar:datum timeValue="1127183700" value="1.50811390446627E7"/> </perfsonar:data>
or something else...
I think units are part of the base "datum" type. So to get your optimization without fiddling with schemas, you could use: <perfsonar:datum timeValue="1127183580" value="7.620117028888889E7" units="bps"/> <perfsonar:datum timeValue="1127183640" value="1.4989345286805557E7"/> <perfsonar:datum timeValue="1127183700" value="1.50811390446627E7"/> By the way, if this is really what your data looks like, I would roughly swap the resolution of the value and the timestamp. -Dan