<div dir="ltr">Hi Matthew,<div><br></div><div><div class="gmail_extra" style>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. <br><br></div><div class="gmail_extra" style>I'll add these corrections to the list of version 2.1 changes.</div><div class="gmail_extra" style><br></div><div class="gmail_extra" style>Brian</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 8, 2014 at 2:33 PM, Matthew Graham <span dir="ltr"><<a href="mailto:mjg@cacr.caltech.edu" target="_blank">mjg@cacr.caltech.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
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.<br>
<br>
The same problem may exist for pullToVoSpace.<br>
<br>
Cheers,<br>
<br>
Matthew</blockquote></div><br><br>
</div></div></div>