Hi Folks, > - Someday mail will be a tenet, and when it becomes one, Implementing "I > want to mail this" by adding MailMessageMixin to the item's superkinds > is too limiting: if the thing you're sending IS the mail message, you > can only mail one item this way, and you can only mail it once (unless > we want to add lots more mechanism to track multiple sendings of an > item). (I bring this up now because we're talking about how invitations > should work.)
I was confused in the past about how stamping as mail and sending related to one another. What I've heard most recently has made more sense to me: - When an item is stamped as an email, it gains a send button - Once an email has been sent or received, its send button turns into an update button Whether updates result in new items or changes to the original item gets us back to the multiple versions of the same item vs. multiple items which are related to one another issue, which I suppose is a Domain Model issue. Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
