On 14.06.2006, at 15:06, Dave Morris wrote:
> Paul Harrison wrote:
>
>> On 14.06.2006, at 13:35, Dave Morris wrote:
>>
>>> Or, it could be sent in a separate SOAP message, which would
>>> require information about the target service, the endpoint URL
>>> and some form of identifier.
>>>
>>> dime-put (other) +wsdl, endpoint, ident
>>
>>
>> This second is a web service in itself - it would need an entire
>> IVOA standard to cover it
>
> It would need _a_ specification, not necessarily IVOA.
> If a 3rd party Grid project already had one defined, then we might
> want to be able to send and receive data from their services too.
>
>> , and what's more I cannot really see a good use case for it.
>
> I don't see a good reason for explicitly excluding it.
> One use case would be for an external service (not part of the
> VOSpace service itself) that stored sensitive data.
> DIME or MTOM with XML signatures would work well for authenticating
> access.
I am not explicitly excluding it for the future, but the current 0.21 VOSpace document does mention this possibility and I think that if anything is said about DIME at all it should be as the direct attachment to the operations in the VOSpace interface rather than as some underspecified alternative. The direct attachment to the methods in the VOSpace interface also has a resonance with the VOStore spec, which had the same mode of operation.
In addition if "dime-put (other) +wsdl, endpoint, ident" transport needs extra metadata to be sent in pushDataFromVoSpace beyond the delivery URI then it cannot be implemented in VOSpace1.0 anyway.....
Paul. Received on 2006-06-14Z15:43:38