james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r722820 - /james/server/trunk/spoolmanager-function/src/main/java/org/apache/james/James.java
Date Wed, 03 Dec 2008 09:28:55 GMT
Author: rdonkin
Date: Wed Dec  3 01:28:54 2008
New Revision: 722820

URL: http://svn.apache.org/viewvc?rev=722820&view=rev
Log:
Some notes about spool management

Modified:
    james/server/trunk/spoolmanager-function/src/main/java/org/apache/james/James.java

Modified: james/server/trunk/spoolmanager-function/src/main/java/org/apache/james/James.java
URL: http://svn.apache.org/viewvc/james/server/trunk/spoolmanager-function/src/main/java/org/apache/james/James.java?rev=722820&r1=722819&r2=722820&view=diff
==============================================================================
--- james/server/trunk/spoolmanager-function/src/main/java/org/apache/james/James.java (original)
+++ james/server/trunk/spoolmanager-function/src/main/java/org/apache/james/James.java Wed
Dec  3 01:28:54 2008
@@ -621,6 +621,29 @@
     }
 
     /**
+     * <p>Note that this method ensures that James cannot be run in a distributed
+     * fashion.</p>
+     * <p>Two instances may return the same ID. 
+     * There are various ways that this could be fixed. 
+     * The most obvious would be to add a unique prefix. 
+     * The best approach would be for each instance to be configured
+     * with a name which would then be combined with the network
+     * address (for example, james.name@mail.example.org) to create a
+     * unique James instance identifier.
+     * </p><p> 
+     * Alternatively, using a data store backed identifier (for example, from a sequence
+     * when DB backed) should be enough to gaurantee uniqueness. This would imply
+     * that the Mail interface or the spool store should be responsible for creating
+     * new Mail implementations with ID preassigned. 
+     * </p><p>
+     * It would be useful for each 
+     * James cluster to have a unique name. Perhaps a random number could be generated by

+     * the spool store upon first initialisation.
+     * </p><p>
+     * This ID is most likely
+     * to be used as message ID so this is probably useful in any case.
+     * </p>
+     * 
      * @see org.apache.james.services.MailServer#getId()
      */
     public String getId() {



---------------------------------------------------------------------
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