Re: 1.0rc1 WSDL issues

From: Dave Morris <dave-at-ast.cam.ac.uk>
Date: Wed, 14 Jun 2006 15:40:01 +0100


Paul Harrison wrote:

> On 14.06.2006, at 13:52, Dave Morris wrote:
>
>> This implies asynchronous transfers, which we have not defined in
>> enough detail yet.
>
> We have asynchronous transfers - are not the push bulk data methods
> asynchronous, web service call finishes before data has arrived?
> Certainly pushDataToVoSpace is....

Yep, you are right, PushdataToVoSpace is asynchronous. However, the client is controlling the push, so it already knows when it has finished sending the data.
We need status callbacks (and status polling) when the server is responsible for doing the transfer itself and the client is not involved (e.g. client asks one service to send to another).

I too would like to implement asynchronous transfers properly, with notification callbacks etc.
However, I thought that we decided these would go into v2.0 because we hadn't finalized exactly how this would work yet.

Getting agreement on v1.0 is proving difficult enough. Lets concentrate on getting v1.0 done and then we can add all the interesting things in v2.x.

Dave   Received on 2006-06-14Z16:40:44