GetData

This defines the service endpoint for a DIME get transfer.

Note, this is not part of the main VoSpace interface. This may be implemented as a capability of a VoSpace service, or it may be implemented as a separate webservice.

When a client requests a DIME get transfer via ExportInit , the VoSpace service replies with the endpoint address of a service that implements this interface, and a URI identifier for the transfer.

If the VoSpace service does not support transfer transactions, then this may be just a URI of a VoSpace data node. However, if the VoSpace service does support transfer transactions, then the URI may point to a data transfer setup by a call to ExportInit .

The content of the identifier is service specific, and the client should not try to interpret it as anything other than an opaque URI.

Parameters

• Target - The transfer URI
  • vos://[service]/000-517-889

Returns

A <node> element, including the node properties.

The content of the node, sent as a DIME attachment.

Throws

• The service will throw a InvalidIdentifier exception if the identifier is not valid.
• The service will throw a ExpiredTransaction exception if the transaction has expired.

• The service may throw an InternalFault exception if an operation fails.
• The service may throw a PermissionDenied exception if the user does not have permissions to perform the operation.

Notes

• DIME is supported in many of the current SOAP toolkits. However, it is a deprecated protocol, and is being replaced by MTOM.
• As toolkit support for MTOM becomes stable, this method will be replaced by a similar MTOM based one.

Questions

• Should we have a version of this that accepts the URI of a data node, enabling clients to get the data directly without setting up a transfer using ExportInit ?
• It does give us a direct 'get' method. However, it also links the VoSpace interface with a specific transfer protocol.
• Current thinking is keep it separate, and look at closer integration if people need it.

-- DaveMorris - 28 Apr 2006