TAPRegExt: sync/async preference

Paul Harrison paul.harrison at manchester.ac.uk
Tue Jul 15 18:22:24 CEST 2025



> On 15 Jul 2025, at 14:41, Gregory MANTELET via dal <dal at ivoa.net> wrote:
> 
> 
> To be honest, I don't like either this false-sync endpoint. Changing that way
> the behavior of this endpoint is clearly a breaking change

What I suggested is a backwards compatible extension for “dumb" clients assuming that they always treat a non-2xx http response is an error. It is still a sync endpoint that can time-out (which could happen in the current UWS/TAP standard definitions) - it is just that the timeout *could* contain information that would allow a slightly less dumb client to see that it might be possible still to obtain the result if they are prepared to wait longer and do the full async protocol. Simple clients do not have to do any more work than before.

Paul.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/dal/attachments/20250715/30ee311c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2893 bytes
Desc: not available
URL: <http://mail.ivoa.net/pipermail/dal/attachments/20250715/30ee311c/attachment-0001.p7s>


More information about the dal mailing list