On 20 Dec, 2006, at 13:07, Brian Kirsch wrote:
On Dec 20, 2006, at 7:17 AM, Grant Baillie wrote:
...
- Currently, there's an SMTPDeliveryStatus class in the mail code
that tracks DRAFT/QUEUED/SENT/ERROR state. Look into unifying this
with the enumerated type above, or for moving the communication-
related Modification values into the mail module somehow. If I
knew how to do this cleanly, I probably would have done it
already, so suggestions are welcome :).
The end goal is to de-couple the notion of a communication from
mail. Thus alternate modes of transport (XMPP for example) could be
used in future versions of Chandler. As such the classes, in
pim.mail that inherit from DeliveryBase including SMTPDelivery can
be factored out of the code and the CommunicationStatus can be used
in its place to track state of mail communications.
Cool, that makes sense: Thanks for the explanation/clarification.
--Grant
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
