Dear Wiki user,

You have subscribed to a wiki page or wiki category on "James Wiki" for change 
notification.

The "JamesArchitecture" page has been changed by SimonFunnell.
http://wiki.apache.org/james/JamesArchitecture?action=diff&rev1=1&rev2=2

--------------------------------------------------

  = JamesArchitecture =
  This is a summary view and some notes on the JamesArchitecture, it attempts 
to provide some conceptual groupings with associated terminolgy. This page is 
not authoritative but its reasonable.
  
- 
{{attachment:W:\ECLIPSE\JamesDocumentation\JamesArchitecture.gif|W:\ECLIPSE\JamesDocumentation\JamesArchitecture.gif}}
+ {{attachment:JamesArchitecture.gif}}
  
  ----
  == Framework ==
  === JamesServer ===
  This is the complete unit, it is installable as a standalone server, deployed 
as component of an existing server or embedded in some other arrangement. The 
JamesServer uses various tools and frameworks to provide the supporting runtime 
for JamesUserServices and JamesServices.
  
+ ==== Unit Responsibility ====
+  * Qualifying infrastructure elements.
+  * Supplying common transport services (TLS support).
+  * Managing the JamesServices and JamesUserServices.
+ 
+ ==== Responsible Roles ====
+ The JamesServer is the responsibility of the Deployer (at runtime) and 
Engineer (at design time).
+ 
  === JamesUserServices ===
  These are a number services that provide implement request/response based 
protocols, they are essentially mail delivery units.
  
+ ==== Unit Responsibility ====
+  * ClientServices
+   * SMTP
+   * POP3
+   * IMAP
+   * NNTP
+  * AdminstratorServices
+   * Remote Manager
+   * Improvements Proposed
+  * DeployerServices
+   * Remote Manager
+   * Improvements Proposed
+ 
  === JamesServices ===
- These are the internal services James uses to support the JamesUserServices, 
they essentially make up the Mail Processing unit. This comprisies of User 
Information Sources, Repositories, the Mailet Container and its related 
resources.
+ These are the internal services James uses to support the JamesUserServices, 
they essentially make up the Mail Processing unit.
+ 
+ ==== Unit Responsibility ====
+  * User Information Sources -RDBMS/LDAP
+  * FetchMail/Mailet Container/Sieve
+  * Spool/Repositories/Mailboxes
+ 
+ ==== Responsible Roles ====
+ JamesServices are the responsibility of Adminstrators (at runtime) and 
Developers (design time).
  
  ----
  == Configuration ==

Reply via email to