I think you're right... I was concerned about servers doing
redirection, so that a client might miss the fact that it's already
seen an archive, but as long as it uses the same identifiers to
locate documents, it should be fine.
On 29/06/2005, at 6:21 AM, Antone Roundy wrote:
If it's for identification rather than retrieval, maybe it could be
an Identity Construct...except Identity Constructs got nuked in
format-06...not necessarily dereferencable. Another option would
be to identify whether you need to continue by checking whether
you've seen the "prev" link before. Would not that be as reliable
as checking the "this" link?
On Wednesday, June 29, 2005, at 12:10 AM, Mark Nottingham wrote:
You need to be able to figure out which documents you've seen
before and which ones you haven't, so you don't recurse down the
entire stack. Although you can come up with some heuristics to
determine when you've seen a document before, most (if not all) of
them can be fooled by particular sequences of entries. Remembering
which ones you've seen (using their 'this' URI) allows you to
easily figure this out.
On 28/06/2005, at 8:48 PM, Antone Roundy wrote:
Thinking a little more about this, I'm not sure what the "this"
link would be used for. The "prev" link seems to be doing all
the work, and especially assuming a "batches of 15" sort of
model, the "this" link seems likely to end up pointing to a
document that's going to disappear soon 14 times out of 15.
--
Mark Nottingham http://www.mnot.net/
--
Mark Nottingham Principal Technologist
Office of the CTO BEA Systems
--
Mark Nottingham http://www.mnot.net/
