On Sun, Apr 29, 2001 at 11:20:44AM -0700, Ian Clarke wrote: > On Sat, Apr 28, 2001 at 01:40:25AM -0400, Travis Bemann wrote: > > > #3 Stacks > > > Supports "stacks", these are a generic name for documents which are > > > updated by appending a higher number each-time. Stacks may be public or > > > private, private stacks are SSKs and can only be added to by the SSK's > > > owner. Public stacks may be verified or unverified. Verified stacks > > > are tied to a private stack which a server can use to indicate that an > > > entry in a public stack has been read. This is useful for submission > > > mechanisms. Finally, stacks may include features to make them more > > > efficient such as combining them with DBRs. > > > Stack support is useful since a client can request that a server perform > > > a stack operation, which may take hours to complete, and terminate > > > before the operation has completed. > > > > This is not enough. For practical reasons, it is necessary to do > > something like have separate enumerations for each day or whatever > > unit of time. > > That is what I was talking about when I mentioned "DBRs" above.
Combining them with DBRs is not enough (for various reasons). For example, you will often have to get old messages with things like EOF News (because you don't constantly download new messages, so you will have to download all of the messages between the present and the last time you downloaded messages, or a fixed period of time if you are using a newsgroup for the first tiem). In addition, DBRs only help slow things down more (because you have to request yet another file
