Persistent TAP uploads

[Mark Taylor]

Markus,

On Mon, 14 Oct 2024, Markus Demleitner via dal wrote:

> Well... by now I figured *something* is better than nothing at all,
> and so I went ahead and put a (functional) sketch of persistent
> uploads into DaCHS.

looks fun.

I *probably* won't implement any client code before I see you next,
but just in case I get bored on a train: what about capability
discoverability?

This almost answers itself: a HEAD request to tap-url/user_tables
returns:

   404: unsupported
   403: supported (but you're not authenticated)
   200: supported (and you are authenticated)

But I don't see a natural way for an unauthenticated user to find out
if unauthenticated persistent uploads are permitted.  However the idea
of an unauthenticated persistent upload is a bit wacky.

Maybe this should just be handled by TAPRegExt - but perhaps a bit
harder to prototype (taplint might give you a hard time?).

Mark

--
Mark Taylor  Astronomical Programmer  Physics, Bristol University, UK
m.b.taylor at bristol.ac.uk          https://www.star.bristol.ac.uk/mbt/