perfsonar development work

[Jason Zurawski <>]

All;

>
>
> After looking closer, it looks like the current state of the services
> is (Roman/Jason - please correct me if I'm wrong):
>
> Time related parameters such as "startTime", "endTime" are assumed to
> be unix strings. (Roman apparently supports nmtime child objects as
> well, but it is not in the interface doc. ;) )


Yes, this is correct (and now that I know Roman supports this, we can
easily make the change).


>
> My suggestion going forward is this:
>
> 1) keep 'startTime' and 'endTime' parameters for at least the next
> major release - perhaps even the one after that. These parameters can
> be specified with String's that will be interpreted as 'unix'
> timestamps (as they are now). Or, they can be an nmtime element - but
> only the TimeStamp variety. (no start/end child elements allowed -
> these would be a semantic error)
>
> 2) add a 'timeRange' parameter (I don't care the name) which is
> specified using a general nmtime element child, which must specify a
> range using the start/end or start/duration syntax.
>
> 3) eventually deprecate 'startTime' and 'endTime' as direct parameters.

Deprecation is fine, although this doesn't seem to be a big deal to have
to ways of describing the 'ranges'.

-jason


-- 

Jason Zurawski, Network Software Engineer
Internet2

office: [+1-202-331-5354]
mobile: [+1-734-846-2900]
fax:    [+1-202-872-6648]

The Internet2 Dynamic Circuit Network:
Unleash your interdomain imagination
http://www.internet2.edu/network/dc/