[4062] in Release_7.7_team
Re: Minutes of 2003-11-05 release team meeting
daemon@ATHENA.MIT.EDU (Robert A Basch)
Wed Nov 5 19:47:41 2003
From: Robert A Basch <rbasch@MIT.EDU>
To: Greg Hudson <ghudson@mit.edu>
Cc: release-team@mit.edu
In-Reply-To: <200311052022.PAA08768@equal-rites.mit.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1068079657.5043.159.camel@anhedonia.mit.edu>
Mime-Version: 1.0
Date: Wed, 05 Nov 2003 19:47:37 -0500
> B. How to identify messages - There are UIDs, which will grow big,
> and sequence numbers, which may have weird properties (like, if you
> have 100 messagse, and you delete one in the middle, the next one
> that comes in might fill in the gap--but that seems very wrong).
A clarification: when a message is expunged, the sequence number
for any subsequent message is decremented, thus filling the gap.
So, in this example, message 100 would be renumbered to 99 (and
an incoming message would be 100). The server sends asynchronous
status updates to clients when the mailbox size changes (this is
apparently how pine deals with this -- it updates its message
sequences almost immediately following an expunge by another
session).
So, there would potentially be a problem whenever the mailbox
is expunged subsequent to the user getting a message sequence
list.
Bob
