On 21 Feb 2003 07:34:59 +0200 Timo Sirainen <[EMAIL PROTECTED]> wrote:
> I'd like to know how you can make a client efficiently handle sequence > numbers. If internal message structure contains just the sequence > number, it has to be updated every time an older message is deleted. > Since it's just memory it's not too slow, but I can't see how that could > be better (from client's point of view) than simply using UIDs where you > don't have to do any updates at all. Sigh. Please go back and read the archives of this group. Have a look at the c-client code. Really, it takes but a moment of thought to figure out how to use sequence numbers efficiently and how to integrate them flawlessly with UID. It also shows why they are useful in efficient client construction. The biggest issue with sequence numbers (in my opinion) is that we haven't used them to their full potential. This is the basis of the "how to do sort, and subsequently thread", extensions debate. That is also water well under the bridge. Cheers. --- Steve Hole Chief Technology Officer - Billing and Payment Systems ACI Worldwide <mailto:[EMAIL PROTECTED]> Phone: 780-424-4922
