Agreed. On a practical level this means we don't have to define all the stuff VOSpace can do and -- more importantly even -- it is easier for the TAP implemention to be a VOSpace client than manage the resources necessary to stage the result itself. you can write a more or less stateless TAP service where a request has a finite lifetime and you don't have to do cleanup and resource management later on.
Pat
On Tuesday 01 May 2007 13:00, Alex Szalay wrote:
> I think that when we get into the async responses, this will
> have to be part of the VOStore/VOSpace story, i.e. the output
> goes into a friendly VOSpace location and sends the handle
> to the result.
>
> --Alex
-- Patrick Dowler Tel/Tél: (250) 363-6914 | fax/télécopieur: (250) 363-0045 Canadian Astronomy Data Centre | Centre canadien de donnees astronomiques National Research Council Canada | Conseil national de recherches Canada Government of Canada | Gouvernement du Canada 5071 West Saanich Road | 5071, chemin West Saanich Victoria, BC | Victoria (C.-B.)Received on 2007-05-01Z22:27:23