james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From da...@apache.org
Subject svn commit: r124520 - /james/server/trunk/src/xdocs/design_objectives.xml /james/server/trunk/src/xdocs/index.xml
Date Fri, 07 Jan 2005 15:52:23 GMT
Author: danny
Date: Fri Jan  7 07:52:22 2005
New Revision: 124520

URL: http://svn.apache.org/viewcvs?view=rev&rev=124520
Log:
removed duplicate para from index.xml
added blurb about standards to design_objectives
Modified:
   james/server/trunk/src/xdocs/design_objectives.xml
   james/server/trunk/src/xdocs/index.xml

Modified: james/server/trunk/src/xdocs/design_objectives.xml
Url: http://svn.apache.org/viewcvs/james/server/trunk/src/xdocs/design_objectives.xml?view=diff&rev=124520&p1=james/server/trunk/src/xdocs/design_objectives.xml&r1=124519&p2=james/server/trunk/src/xdocs/design_objectives.xml&r2=124520
==============================================================================
--- james/server/trunk/src/xdocs/design_objectives.xml	(original)
+++ james/server/trunk/src/xdocs/design_objectives.xml	Fri Jan  7 07:52:22 2005
@@ -1,28 +1,38 @@
 <?xml version="1.0"?>
-
 <document>
-
- <properties>
-  <title>Design Objectives</title>
-  <author email="site-dev@james.apache.org">James Project Web Team</author>
- </properties>
-
-<body>
-
-<section name="Design Objectives">
-<p>These are some of the currently implemented features:</p>
-<p><i><b>Complete portability</b></i>  Apache James is be a
100% pure Java application
+  <properties>
+    <title>Design Objectives</title>
+    <author email="site-dev@james.apache.org">James Project Web Team</author>
+  </properties>
+  <body>
+    <section name="Design Objectives">
+      
+      <subsection name="features">
+        <p>These are some of the currently implemented features:</p>
+        <p>
+          <i>
+            <b>Complete portability</b>
+          </i>  Apache James is be a 100% pure Java application
        based on the Java 2 platform and the JavaMail 1.3 API.
   </p>
-  <p><i><b>Protocol abstraction</b></i>  Unlike other mail
engines, protocols are seen only
+        <p>
+          <i>
+            <b>Protocol abstraction</b>
+          </i>  Unlike other mail engines, protocols are seen only
        like "communication languages" ruling comunications between clients and
        the server. Apache James is not be tied to any particular protocol but
        follow an abstracted server design (like JavaMail did on the
        client side)</p>
-    <p><i><b>Complete solution</b></i>  the mail system is
able to handle both mail
+        <p>
+          <i>
+            <b>Complete solution</b>
+          </i>  the mail system is able to handle both mail
        transport and storage in a single server application. Apache James
        works alone without the need for any other server or solution.</p>
-    <p><i><b>Mailet support</b></i>  Apache James supports
the Apache Mailet API. A Mailet
+        <p>
+          <i>
+            <b>Mailet support</b>
+          </i>  Apache James supports the Apache Mailet API. A Mailet
        is a discrete piece of mail-processing logic which is incorporated into
        a Mailet-compliant mail-server's processing. This easy-to-write,
        easy-to-use pattern allows developers to build powerful customized mail
@@ -30,16 +40,65 @@
        mail-to-fax or mail-to-phone transformer, a filter, a language translator, a mailing
        list manager, etc. Several Mailets are included in the JAMES
        distribution (see <a href="documentation_2_1.html">documentation</a>).</p>
-    <p><i><b>Resource abstraction</b></i>  Like protocols,
resources are abstracted and,
+        <p>
+          <i>
+            <b>Resource abstraction</b>
+          </i>  Like protocols, resources are abstracted and,
        accessed through defined interfaces (JavaMail for transport, JDBC for
        spool storage or user accounts in RDBMS's, Apache Mailet API). The server is
        highly modular and reuse solutions from other projects.</p>
-    <p><i><b>Secure and multi-threaded design</b></i>  Based
on the technology developed
+        <p>
+          <i>
+            <b>Secure and multi-threaded design</b>
+          </i>  Based on the technology developed
        for the Apache JServ servlet engine, Apache James has a careful,
        security-oriented, full multi-threaded design, to allow performance,
        scalability and mission-critical use.</p>
-    <p>Anything else you may want if you help us write it :-)</p>
-</section>
-
-</body>
+        <p>Anything else you may want if you help us write it :-)</p>
+      </subsection>
+      <subsection name="standards compliance">
+        <p>It is the existence of published "open" standards which 
+allows independant teams to develop interoperable software.
+<br/>James attempts to support a number of these standards most of which are 
+IETF RFC's and in the areas covered by these standards the published standard 
+is our requirements document.
+<br/>This sometimes leads to confusion where behaviour is not 
+the subject of a relevant standard, or conflict where common 
+(de-facto) behaviour is actually at odds with a supported standard.
+<br/>We believe that it is our responsibility to adhere to the published standard.

+If we allow our implementation to deviate it means that we are tacitly encouraging 
+the situation whereby interoperability is no longer guarenteed by standards 
+compliance alone, but also requires access to undocumented and possibly 
+even commercially licenced technology. There is no easy route for a 
+newcomer to aquire these secrets, and interoperabilty 
+becomes something only available to the elite.
+        </p>
+        <p>The James policy for issues of non-compliance tries to tread the fine line
+between a pragmatic acceptance of other people's misinterpretation of the
+RFC's and an evangelical defence of open standards as the key to freedom of interoperation.
+        </p>
+        <p>
+In practice this policy is that certain well argued of cases of
+non-compliance which can be *safely* worked around, will be tolerated by
+James.
+</p>
+        <p>
+In cases (like jira issue JAMES-344 ) where variance from a published standard is
+required it is desirable that this functionality is disabled in James by default,
+it must be prominently and clearly documented that this causes James 
+to violate the relevant standard, and should be enabled by explicit 
+configuration, making its use a conscious decision of the user rather 
+than an decision taken by the James team.
+</p>
+        <p>
+In cases where the required behaviour is not within the scope of any standard which
+James claims to support (such as behaviour which is a de-facto standard or
+an <i>internet draft</i> RFC but not yet subject of a <i>standards track</i>
RFC) it is
+acceptable to implement the behaviour so long as it is adequately
+documented (for instance by refrence to an <i>internet draft</i> or 
+other public document) and users can be clear about what to expect from James.
+</p>
+      </subsection>
+    </section>
+  </body>
 </document>

Modified: james/server/trunk/src/xdocs/index.xml
Url: http://svn.apache.org/viewcvs/james/server/trunk/src/xdocs/index.xml?view=diff&rev=124520&p1=james/server/trunk/src/xdocs/index.xml&r1=124519&p2=james/server/trunk/src/xdocs/index.xml&r2=124520
==============================================================================
--- james/server/trunk/src/xdocs/index.xml	(original)
+++ james/server/trunk/src/xdocs/index.xml	Fri Jan  7 07:52:22 2005
@@ -12,34 +12,21 @@
       <p>James requires Java 1.4 (For further information you may want to search the
web, our <a href="http://www.mail-archive.com/server-dev@james.apache.org/">dev</a>
and <a href="http://www.mail-archive.com/server-user@james.apache.org/">user</a>
mail archives or our <a href="http://wiki.apache.org/james">wiki</a>).</p>
     </section>
     <section name="news">
+
     <subsection name="2005">
 
      <h3>James PMC react to the closure of Apache Avalon.</h3>
       <p>James PMC would like to reassure all of our users that James is alive and
well. All of the James team have kept abreast of the Avalon developments culminating in the
closure of the Avalon project and dispersal of its codebase. We are are keen to stress that
this has little impact on our ability to support and develop James in both the short and long
terms.<br/>Over the coming months we will be finalising and publishing a road map for
James which will address all of the specific concerns raised by Avalon's closure, but rest
assured James' future is safe, and we have enthusiasm and plans aplenty.<br/> In the
meantime we would like to extend our best wishes to all our friends from Avalon, here's luck
with your future projects guys!<br/> If you are at all concerned please subscribe to
the server-user mailing list and raise your points there. - 05/Jan/2005</p>
-    
+
       <h3>James source has moved to "Subversion"</h3>
       <p>Subversion is a version control system like CVS, but it has advantages over
CVS for Apache Software Foundation (ASF) projects.<br/> In common with all other ASF
projects we have reviewed our use of CVS and migrated our code to Subversion.<br/>
 Have a look at this <a href="FAQ.html#17">FAQ</a> for further details. - 05/Jan/2005</p>
       <p/>
       </subsection>
       <subsection name="2004">
+
       <h3>James v2.2.0</h3>
-      <p>
-        <a href="#releases">James v2.2.0</a> is released.</p>
-      <h3>James featured on IBM developerWorks</h3>
-      <p>
-Claude Duguay has written two excellent articles on <a href="http://james.apache.org/">James</a>
for
-<a href="http://www.ibm.com/developerworks/">IBM Developer works</a>
-        <br/>
-[<a href="http://www-106.ibm.com/developerworks/java/library/j-james1.html">article1</a>]
-An introduction to Apache's James enterprise e-mail server.<br/>
-[<a href="http://www-106.ibm.com/developerworks/java/library/j-james2.html">article2</a>]
-Build e-mail based applications with Matchers and Mailets.
-</p>
-      <p>
-        <b>James v2.2.0</b>
-        <br/>
-        <a href="#releases">James v2.2.0</a> is released.</p>
+      <p><a href="#releases">James v2.2.0</a> is released.</p>
       <h3>James featured on IBM developerWorks</h3>
       <p>
 Claude Duguay has written two excellent articles on <a href="http://james.apache.org/">James</a>
for

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message