On 7 Dec, 2006, at 21:47, Jeffrey Harris wrote:
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. ;) )
Changing email is definitely related, and it's certainly confusing
at first.
One way to look at this is to think about how Drafts work in many
mail clients. To the end-user, it looks as if they're editing an
email, whereas in reality the client is creating a new RFC(2)822
message and wiping out the original when the Draft is saved.
The crux of the communication stamp is that the same item can be
edited
and shared throughout a process of sending drafts, normally sending
the
item, or sending updates after the item's been normally sent.
So when I talked about emails, I was referring to updates (i.e.,
drafts
of not-yet-sent items, and updates to previously sent items).
Now that I think about it, I'm not actually sure what the payload of a
normal send should be. Maybe the same as an update?
Well, I think we'd discussed on IRC sending out two EIM blobs in
emails (the previous and current versions). Presumably, for a first-
time send, the previous version wouldn't be there. But otherwise,
yes, pretty much the same.
--Grant
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
