We had alot of discussion of this and my impression is that the people who feel strongly aren't going to budge, that in general a server is not going to guarantee that a result set will persist.
There is a time-to-live parameter, returned in every response, and although it's not a guarantee (just a "hint") it might provide some level of confidence in the persistence of the result set, but I think that's about the best we're going to do.
Theo van Veen wrote:
> In case a resultset is combined with other search terms, it doesn't matter how the server handles this, but in case one wants to request a specific record from a list (for example to get another format) it does matter whether the query is re-executed or that the record is obtained from the resultset, because you want exactly that specific record.
> Perhaps it would be a good compromise to distinguish between two cases:
> 1) the resultset as a separate parameter in which case it refers to a specific set of records and is used instead of a search query
> 2) the resultset as part of the query in which case is doesn't matter how the server handles the query.
> So either a query is specified or a resultset is specified (and the query may contain a resultsetid).