pushToVoSpace to .auto

[Matthew Graham]

Hi Brian,

copyNode and moveNode already specify this:

If an autogenerated URI for the destination was specified in the request then its value SHALL be specified as a result in the Results List for the completed transfer with the id of "destination":

	Cheers,

	Matthew

On Dec 8, 2014, at 5:21 PM, Brian Major wrote:

> Hi Matthew,
> 
> Saving the URI in the results sounds like the right way to do it.  copyNode and moveNode are transfers and use .auto, so they should also mention how to get the autogenerated URI.  pullToVoSpace doesn't mention .auto, but should.  
> 
> I'll add these corrections to the list of version 2.1 changes.
> 
> Brian
> 
> 
> On Mon, Dec 8, 2014 at 2:33 PM, Matthew Graham <mjg at cacr.caltech.edu> wrote:
> Hi,
> 
> There is an issue with pushToVoSpace with a reserved endpoint, i.e., target=vos://.../.auto. The spec does not state where the autogenerated URI for the node is reported back to the client. Since this is a data transfer there is no Node representation returned. I would suggest that it is added as another result in the transfer results.
> 
> The same problem may exist for pullToVoSpace.
> 
>         Cheers,
> 
>         Matthew
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/dsp/attachments/20141208/2685b7a6/attachment.htm>