User:Emre/tb/architecture/diagrams

About this work

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

The following is the UML diagrams of (some) major components of Thunderbird. I started this work to document and share my understanding of Thunderbird architecture while working on a threading bug. This is a work in progress and I am planning to add more diagrams over time. I don't plan to cover everything, just important stuff.

I use only the basic elements of UML, and try to keep it simple as much as possible. I deliberately use some elements non-normative way, don't expect a perfect UML diagram. You can find the description of the common elements in the legend.

Core Components

• Message Incoming Server
  • interface
  • Implementation
• Account Manager
  • interface
  • implementation
• Message Folder
  • interface
• Address Book
• Message Database
  • interface
  • implementation
    • NewsDatabase, MailDatabase, ImapMailDatabase
• Message Database Folder
  • Implementation

Protocol Implementation

• IMAP
  • Sequence diagrams
    • System Startup
    • System Shutdown
    • 'Get Mail' button clicked
    • OnBiffTimer event
    • Connection Error case
    • Message Delete
    • New Message
  • Class diagrams
    • nsIImapIncomingServer interface
    • nsImapIncomingServer class
    • nsIImapProtocol interface
    • nsImapProtocol class

• POP3
  • nsPop3IncomingServer
  • nsIPop3Protocol
  • nsIPop3IncomingServer

• NNTP
  • NNTP Implementation Notes

• RSS