Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 81354 invoked from network); 13 Oct 2004 09:36:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 13 Oct 2004 09:36:21 -0000 Received: (qmail 20063 invoked by uid 500); 13 Oct 2004 09:35:47 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 19962 invoked by uid 500); 13 Oct 2004 09:35:46 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 19865 invoked by uid 99); 13 Oct 2004 09:35:44 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of l.garulli@gmail.com designates 64.233.170.203 as permitted sender) Received: from [64.233.170.203] (HELO mproxy.gmail.com) (64.233.170.203) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 13 Oct 2004 02:35:43 -0700 Received: by mproxy.gmail.com with SMTP id 75so764539rnl for ; Wed, 13 Oct 2004 02:35:38 -0700 (PDT) Received: by 10.38.165.75 with SMTP id n75mr2312707rne; Wed, 13 Oct 2004 02:35:38 -0700 (PDT) Received: by 10.38.102.64 with HTTP; Wed, 13 Oct 2004 02:35:38 -0700 (PDT) Message-ID: Date: Wed, 13 Oct 2004 11:35:38 +0200 From: Luca Garulli Reply-To: Luca Garulli To: dev@cocoon.apache.org Subject: Daisy as CMS: why don't use JDO? Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi, I give a look to the Daisy project (http://new.cocoondev.org/daisy/2) presented these days to the GetTogheter event. It seems much interesting, but as repository uses RDBMS. Currently only MySQL and InnoDB are supported as db. Why don't use JDO for the persistence? JDO allows to Daisy to be datastore independent. So you can run Daisy on top of an ODBMS or RDBMS or again the file system. Furthermore JDO support caching to achieve the best performance. I think JDO can give much more flexibility (and performance) to Daisy. What do you think? bye, Luca Garulli OrienTechnologies.com (the light ODBMS, all in one JDO solution)