TAP 1.0: Substantive comments.

[Patrick Dowler]

On Monday 31 August 2009 13:04:50 you wrote:
> If this is permitted for other parameters then I'd want to try to treat
> this the same for file uploads as everything else.  As I see it the cost
> is that we need to preserve parameters that might be file upload
> parameters until we get the RUN request.  But I think the typical
> implementation is going to preserve all of the parameters in some
> fashion anyway until the RUN request is made so the only real difference
> is that these will be longer than most.

On Monday 31 August 2009 13:05:39 you wrote:
> My conclusion is we don't need to say anything special about UPLOAD
> where UWS is concerned.

OK, that makes sense. It is true that in our UWS framework the generic code 
collects everythijng together and service-specific (eg TAP) code only sees it 
when the job runs.

Do we have any feeling/sense on a scheme for the URI? inline? 

-- 

Patrick Dowler
Tel/Tél: (250) 363-0044
Canadian Astronomy Data Centre
National Research Council Canada
5071 West Saanich Road
Victoria, BC V9E 2M7

Centre canadien de donnees astronomiques
Conseil national de recherches Canada
5071, chemin West Saanich
Victoria (C.-B.) V9E 2M7