Return-Path: Delivered-To: apmail-incubator-jackrabbit-dev-archive@www.apache.org Received: (qmail 19521 invoked from network); 21 May 2005 07:48:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 21 May 2005 07:48:56 -0000 Received: (qmail 33904 invoked by uid 500); 21 May 2005 07:48:56 -0000 Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jackrabbit-dev@incubator.apache.org Delivered-To: mailing list jackrabbit-dev@incubator.apache.org Received: (qmail 33889 invoked by uid 99); 21 May 2005 07:48:56 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.28) with ESMTP; Sat, 21 May 2005 00:48:54 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 41212299 for ; Sat, 21 May 2005 09:48:52 +0200 (CEST) Message-ID: <1731647668.1116661732265.JavaMail.jira@ajax.apache.org> Date: Sat, 21 May 2005 09:48:52 +0200 (CEST) From: "Jukka Zitting (JIRA)" To: jackrabbit-dev@incubator.apache.org Subject: [jira] Commented: (JCR-91) JDBCPersistenceManager contribution In-Reply-To: <1466966885.1112223150010.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/JCR-91?page=comments#action_65915 ] Jukka Zitting commented on JCR-91: ---------------------------------- What's the general feeling on the JDBC PM, should it be included in Jackrabbit core? I would be in favor of including it as the default non-filesystem persistence manager. A quite common web setup uses a fault-tolerant backend database server and a performance-tuned web frontend server. The JDBC persistence manager would be a great enabler for such setups until the RMI, Webdav, or other full model 3 solutions reach production quality. > JDBCPersistenceManager contribution > ----------------------------------- > > Key: JCR-91 > URL: http://issues.apache.org/jira/browse/JCR-91 > Project: Jackrabbit > Type: New Feature > Reporter: Edgar Poce > Priority: Minor > Attachments: 05-03-30-jdbc-persistence.zip, 05-04-06-jdbc-persistence.zip, 05-05-12-jdbc-persistence.zip > > A JDBC based PersistenceManager -- 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