[Chandler-dev] Edit/update (email sharing) model thoughts

[Phillip J. Eby]

At 05:12 PM 12/7/2006 -0800, Jeffrey Harris wrote:
>Our discussion today focused a lot on the concept of a message-id.  In
>the standard email universe, every email should have a unique
>message-id.  When sharing emails that are changing, it seems to make
>sense to change the email's message-id (while leaving the item UUID the
>same), because it's really a different message.  These message-ids have
>no order, they're just unique identifiers.  But they could be used to
>give a reasonably coherent picture of which updates have applied to items.

I'm a little bit confused - I've been assuming that the process of sharing 
items *via* email is entirely orthogonal to whether the items *being* 
shared are themselves emails.  In other words, for sharing purposes, I'm 
assuming that there are distinct email messages carrying update "payloads", 
and that these emails need not be items at all; they're just a transport 
mechanism and it doesn't matter whether they are ever seen or edited in the 
UI at all.  In other words, I'm thinking of email as just a background 
transport mechanism for sharing protocol transmissions.

That being the case, it would be helpful to know which kind of emails 
you're talking about here, and throughout your message.  :)  Without that 
information, I can't tell what the rest of your post is proposing, or what 
problem it's intended to solve.

(I also have trouble wrapping my brain around the idea of a "changing" 
email, but that may or may not be related. ;) )