r1 - 04 Aug 2004 - 15:59:00 - MorgenSagenYou are here: OSAF >  Journal Web  >  ContributorNotes > MorgenSagenNotes > MorgenSagen20040804
  • Need to figure out the framework for how the UI interacts with the SMTP service
    • How does the UI indicate to the SMTP service that one or more email items are ready to send
    • How does the service feed email status back up to the UI
    • Possibility:
      1. The UI creates email items
      2. While being edited, those email items have their status set to "Draft"
      3. When the user clicks Send, the UI changes the status of an email to "Ready", and calls an SMTP service method, passing the item to send
      4. The SMTP service does any pre-flight checks and can return an error condition from the method immediately (setting the status back to "Draft")
      5. If the email item looks ok, the SMTP service asynchronously attempts to send the message (setting the status to "Sent")
      6. If an error such as "no such user" occurs, the SMTP service sets the email item's status to "Error" (and somehow alerts the app -- through notifications?)
  • I think there are 3 classes of errors:
    1. Submit-time errors (malformed address, for example) determined by the SMTP layer itself, reported synchronously, as an exception raised from the "send message" method
    2. SMTP-Connection-time errors (no such user, no such domain, others?), determined relatively quickly, reported to app asynchronously
    3. Later-occurring errors (tried to send for 3 days and giving up, for example), determined up to days later, reported to app asynchronously
  • Can we do anything special with bounces? Can we determine which sent item it corresponds to?
  • Meet on Thursday to go over user experience requirements

  • Look into doctests as a way to augment our external unit tests, especially as a way to provide better documentation

  • Talking again with Jeffrey about the state of the generated schema documentation; I suggested a couple possibilities:
    • I write a little bit of code which generates an XML file based on all the schema items in the repository, and Jeffrey transforms that
    • That little bit of code produces a set of HTML files directly

  • Looking at Donn/John's renderer/editor notes; think about how that could be applied to the sharing preferences dialog

-- MorgenSagen - 04 Aug 2004

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.