User:Emre/tb/architecture/diagrams: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 20: Line 20:
= Protocol Implementation =
= Protocol Implementation =
* <b> IMAP </b>
* <b> IMAP </b>
** Sequence diagrams;
** Sequence diagrams  
***[[User:Emre/tb/architecture/diagrams/imap/sequence#System%20Startup | System Startup]]
***[[User:Emre/tb/architecture/diagrams/imap/sequence#System%20Startup | System Startup]]
***[[User:Emre/tb/architecture/diagrams/imap/sequence#System%20Shutdown | System Shutdown]]
***[[User:Emre/tb/architecture/diagrams/imap/sequence#System%20Shutdown | System Shutdown]]
Line 27: Line 27:
***[[User:Emre/tb/architecture/diagrams/imap/sequence#Connection%20Error | Connection Error case]]
***[[User:Emre/tb/architecture/diagrams/imap/sequence#Connection%20Error | Connection Error case]]
***[[User:Emre/tb/architecture/diagrams/imap/sequence#Message%20Delete | Message Delete]]
***[[User:Emre/tb/architecture/diagrams/imap/sequence#Message%20Delete | Message Delete]]
** nsImapIncomingServer class
***[[User:Emre/tb/architecture/diagrams/imap/sequence#Message%20New | New Message]]
** nsIImapIncomingServer class
** Class diagrams
** nsImapProtocol class
*** [[User:Emre/tb/architecture/diagrams/imap/static#nsIImapIncomingServer | nsIImapIncomingServer interface]]
** nsIImapProtocol interface
*** [[User:Emre/tb/architecture/diagrams/imap/static#nsImapIncomingServer | nsImapIncomingServer class]]
*** [[User:Emre/tb/architecture/diagrams/imap/static#nsIImapProtocol | nsIImapProtocol interface]]
 
* <b> POP3 </b>
* <b> POP3 </b>
** nsPop3IncomingServer
** nsPop3IncomingServer

Revision as of 17:51, 14 April 2008

About this work

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.

Components

Protocol Implementation

  • POP3
    • nsPop3IncomingServer
    • nsIPop3Protocol
    • nsIPop3IncomingServer
  • NEWS
  • RSS