[TAP] sync vs async - time outs

[Guy Rixon]

The TAP drafts so far don't define the TAP capability structure; it's  
one of the important things left to do. A timeout parameter is a  
reasonable thing to have. It won't be specified by VOSI - VOSI  
doesn't define protocol-specific capabilities,  but VOSI lets you  
read it directly from the service rather than from the registry.

On 3 Mar 2009, at 16:53, Gerard wrote:

> Dear colleagues
>
> Guy wrote:
> > However, I see no reason why a TAP installation that always operates
> > quickly has to have the asynchronous mode. I would be happy for the
> > asynchronous interfaces to be made optional; but only on the
> > understanding that most TAP services will need them and that  
> software
> > authors be prepared to add them when that need is discovered.
> >
> I support this, but think we should let a service specify what they  
> think is "quickly".
>
> If I am not mistaken the current TAP spec does not explicitly  
> specify a possible query timeout parameter.
> I think every service will actually implement such a timeout,  
> whether /sync or /async.
> (As Guy writes as well, it is very easy to write queries that would  
> run "forever".)
> Is such a parameter part of the VOSI metadata?
> If not I propose it is added to the TAP specification.
>
> best regards
>
> Gerard
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/dal/attachments/20090303/8c793287/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2104 bytes
Desc: not available
URL: <http://www.ivoa.net/pipermail/dal/attachments/20090303/8c793287/attachment-0003.bin>