new UWS 1.1 WD -- mime and job list

[Kristin Riebe]

Hi Grid,

I would also very much like some kind of format or mime attribute to uws 
result, e.g. like this:

<uws:result id="xxx" format="csv" ...>

In our case we have a UWS service that returns results as csv-file, 
ascii-votable, votable binary I or II. Currently, we list all 4 
possibilities with uws:results.
But a general client can't distinguish between a query that returns 
multiple results with *different content* and *different formats* of the 
same content.

A format- or mime-attribute could help a lot here. I think in that case 
I would also prefer if the result id could be the same, if only the 
formats are different (though generally result ids should be unique).
Or is there any other mechanism already in place to handle this?


We recently came across another problem of our application: we have 
users with hundred thousands of jobs, so that our web application ran 
out of memory when the job list should have been returned.
We consider some kind of pagination now or restricting the returned list 
to the latest 1000 jobs or so.
Maybe such a pagination could be considered for UWS 2.

Also, in that context, I would prefer if the location header in the 
response after deleting a job does not necessarily have to point to the 
job list, since then again we get into trouble each time one of the many 
jobs is deleted. A simple reponse confirming a successful deletion could 
be enough.

Cheers,

Kristin



Am 30.09.2014 17:32, schrieb Grégory Mantelet:
> Hello Grid,
>
> I may have a suggestion of modification of the current UWS standard. I
> probably show up a little late, but what I am suggesting is, according
> to me, a minor modification and should not impact at all any existing
> UWS implementation (including in the TAP protocol).
>
> So, I am wondering whether it would be possible to add (or at least to
> allow) the 2 following optional attributes for the 'result' item?
>
>      a/ 'mime', or any other name that would suggest an attribute
> informing about the type of result. I think a MIME type as value of this
> attribute would be a good idea.
>
>      b/ 'size' which will give the size in bytes of the document
> proposed as result. I think users could be interested in a such piece of
> information ; they would know how big is the result they have to
> download. But I think it is particularly useful when several results are
> available.
>
>      (b.bis/ In TAP, I think the information about the number of rows
> contained in the result would be also interesting for some clients. But
> I do not know how to provide this information in the 'result' item.
> Probably an attribute "rows", but it would be probably too much in
> relation with the TAP protocol rather than applying to every kinds of
> UWS implemention.)
>
> So, what is your opinion about the addition of these two attributes?
> Do you think some users may be interested by them?
> And finally, I don't know whether such modifications make sense, but if
> they do, should they be integrated in the new version 1.1 or in a next one?
>
> Regards,
> Grégory
>
> PS: For the moment, I add these 2 attributes in my UWS library...which
> is of course not valid in regard of the XML schema. That's why, for the
> next coming soon version of my library, I am going to fix these
> non-standard attributes by hiding them. However, if it turns out that it
> makes sense to have such additional information, I will be ready to show
> them again later.
>
>
>
> On 30.09.2014 15:50, Paul Harrison wrote:
>> Hi,
>>
>> I have uploaded a new version of the UWS 1.1 WD to
>> http://www.ivoa.net/documents/UWS/20140930/ which contains changes
>> which are largely as a result of the discussion that happened in this
>> thread http://mail.ivoa.net/pipermail/grid/2014-June/002609.html
>>
>> In summary the main change from the previous version is that the
>> blocking behaviour introduced in that version has been moved from a
>> specific custom endpoint to being signalled my a ?WAIT query parameter
>> on the /{jobs}/{job-id} endpoint.
>>
>> I think that this WD now represents something that could be promoted
>> to a PR if we have some reference implementations - any willing
>> volunteers?
>>
>> Regards,
>>     Paul.
>>
>> p.s. as usual the source of the WD can be seen/edited in volute
>> http://volute.googlecode.com/svn/trunk/projects/grid/uws/doc/UWS.html
>
-- 
-----------------------------------------------------------------
| Dr. Kristin Riebe
| eScience & GAVO
|
| Email: kriebe at aip.de
| Phone: +49 331 7499-377
| Room:  B6/25
-----------------------------------------------------------------
| Leibniz-Institut für Astrophysik Potsdam (AIP)
| An der Sternwarte 16, D-14482 Potsdam
| Vorstand: Prof. Dr. Matthias Steinmetz,  Dr. Ulrich Müller    	
|
| Stiftungsverzeichnis Brandenburg: 26 742-00/7026
-----------------------------------------------------------------