Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jackrabbit-dev@incubator.apache.org
Message-ID: <407268243.1121415191082.JavaMail.jira@ajax.apache.org>
Date: Fri, 15 Jul 2005 10:13:11 +0200 (CEST)
From: "Marcel Reutegger (JIRA)" <jira@apache.org>
To: jackrabbit-dev@incubator.apache.org
Subject: [jira] Created: (JCR-169) Make Jackrabbit clusterable
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Make Jackrabbit clusterable
---------------------------

         Key: JCR-169
         URL: http://issues.apache.org/jira/browse/JCR-169
     Project: Jackrabbit
        Type: New Feature
  Components: core  
    Reporter: Marcel Reutegger
    Priority: Minor


This jira issue discusses the technical implications on the current design of Jackrabbit to introduce clustering.

Particularly the following areas require thorough investigation:

- SharedItemStateManager and its cache
    - cache integrity
    - cache design: look aside, write through?
    - hook for distributed cache, interface?
    - isolation level
    - transaction integrity within Jackrabbit, interaction with transient layer
- VirtualItemStateProvider
    - same strategy as SharedItemStateManager?
- Search index
    - single or per cluster node index?
- Observation

Please state more areas if needed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira