Implementation thoughts on discussion points
Guy Rixon
gtr at ast.cam.ac.uk
Wed Oct 7 01:42:43 PDT 2009
On 6 Oct 2009, at 22:33, Matthew Graham wrote:
> [...]
> I thought that we had agreed in Strasbourg that there was no
> inherent mapping between the vos:// URI and the http:// one but that
> one would use a registry to resolve the correct VOSpace endpoint.
> However, the location relative to the root node of the space would
> remain unchanged. Thus:
>
> vos://xyz.com!vospace/mydir/myimg/mydata.fits
>
> would use the registry to figure out the HTTP URL of the root node
> (e.g. http://efg.com/vospace) and then the file would be :
>
> http://efg.com/vospace/mydir/myimg/mydata.fits.
Yes, that's what I thought, and it answers my concerns. But that
approach is not what is written in the draft at
http://www.ivoa.net/internal/IVOA/IvoaGridAndWebServices/WD-VOSpace-2.0-20090513.doc
Cheers,
Guy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/vospace/attachments/20091007/a55f8d54/attachment-0001.html>
More information about the vospace
mailing list