lifetime of user-created tables

[pdowler]

In the existing TAP upload mechanism, upload tables are transient: they exist for a single query and must be uploaded as part of each query to be re-used.

The user-managed table API can be used as an improvement over the transient uploads by creating/uploading once and re-using the table for multiple queries. The TAP service would still probably have/enforce a finite lifetime and if so, this needs to be communicated to the client.

A client may want to renew or extend the lifetime of such a table.

[brianmajor]

If a TAP 1.1 service supports these two use cases:

1. the one you mention: table upload for a finite period to support joins on multiple subsequent queries, and
2. table upload for the purposes of long-term publishing

And if the service has a say in determining how a table can persist, how is it to know which of these use cases the client intends? Does the client need to convey the desired lifetime somehow?