User:Emre/tb/architecture/diagrams: Difference between revisions
Jump to navigation
Jump to search
| Line 19: | Line 19: | ||
= 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%20Shutdown | System Shutdown]] | |||
***[[User:Emre/tb/architecture/diagrams/imap/sequence#Get%20Mail%20Button%20clicked | 'Get Mail' button clicked]] | |||
***[[User:Emre/tb/architecture/diagrams/imap/sequence#OnBiffTimer | OnBiffTimer event]] | |||
***[[User:Emre/tb/architecture/diagrams/imap/sequence#Connection%20Error | Connection Error case]] | |||
***[[User:Emre/tb/architecture/diagrams/imap/sequence#Message%20Delete | Message Delete]] | |||
** nsImapIncomingServer class | ** nsImapIncomingServer class | ||
** nsIImapIncomingServer class | ** nsIImapIncomingServer class | ||
Revision as of 05:48, 11 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
- Incoming Server
- Interface
- Implementation
- 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