User:Emre/tb/architecture/diagrams: Difference between revisions
Jump to navigation
Jump to search
Line 8: | Line 8: | ||
= Components = | = Components = | ||
* <b>Incoming Server</b> | * <b>Message Incoming Server</b> | ||
** | ** [[User:Emre/tb/architecture/diagrams/messageincomingserver#interface | interface]] | ||
** Implementation | ** [[User:Emre/tb/architecture/diagrams/messageincomingserver#Implementation | Implementation]] | ||
* <b>Account Manager</b> | * <b>Account Manager</b> | ||
** [[User:Emre/tb/architecture/diagrams/accountmanager | interface and implementation]] | ** [[User:Emre/tb/architecture/diagrams/accountmanager | interface and implementation]] |
Revision as of 06:47, 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
- Message Incoming Server
- Account Manager
- Message Folder
- Address Book
Protocol Implementation
- IMAP
- Sequence diagrams;
- nsImapIncomingServer class
- nsIImapIncomingServer class
- nsImapProtocol class
- nsIImapProtocol interface
- POP3
- nsPop3IncomingServer
- nsIPop3Protocol
- nsIPop3IncomingServer
- NEWS
- RSS