Hi Philip, > Perhaps we shouldn't have items for email addresses, or at least not > allow changes to EmailAddress.emailAddress. It seems to me that > allowing the emailAddress attribute to change effectively would corrupt > your mail sending/receiving history by making messages appear to have > come from/gone to different addresses than was actually the case.
+1 to not allowing changes to email addresses, I don't see any use cases for that. If a user adds a personality or changes their email address, we'll almost certainly want to relate the old email address and the new through a contact, which wouldn't require changing an address. In the current Chandler world, there aren't really any contacts so I don't know of a lot of benefit associated with email addresses being items. Once we have contacts I can imagine lots of utility in birefs between contacts, email addresses, and messages. So, if we disabled changes to the emailAddress attribute of EmailAddress objects, would observers solve the problem Brian's interested in? Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
