Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 47992 invoked from network); 19 Jan 2005 18:57:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 19 Jan 2005 18:57:43 -0000 Received: (qmail 98008 invoked by uid 500); 19 Jan 2005 18:57:42 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 97981 invoked by uid 500); 19 Jan 2005 18:57:42 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 97968 invoked by uid 99); 19 Jan 2005 18:57:42 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from e31.co.us.ibm.com (HELO e31.co.us.ibm.com) (32.97.110.129) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 19 Jan 2005 10:57:41 -0800 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e31.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j0JIvYm4153690 for ; Wed, 19 Jan 2005 13:57:34 -0500 Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay04.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j0JIvYjI280724 for ; Wed, 19 Jan 2005 11:57:34 -0700 Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j0JIvYea005827 for ; Wed, 19 Jan 2005 11:57:34 -0700 Received: from debrunners.com (dyn9-72-133-60.usca.ibm.com [9.72.133.60] (may be forged)) by d03av04.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j0JIvXYj005795 for ; Wed, 19 Jan 2005 11:57:33 -0700 Message-ID: <41EEAD7C.7020108@debrunners.com> Date: Wed, 19 Jan 2005 10:57:00 -0800 From: Daniel John Debrunner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4.1) Gecko/20031008 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derby Development Subject: Re: Derby architecture/design documents References: <3dee901305011721231508061c@mail.gmail.com> <41ED5411.7070302@bristowhill.com> <001201c4fd9b$2eb50530$1401a8c0@rpws002> In-Reply-To: <001201c4fd9b$2eb50530$1401a8c0@rpws002> X-Enigmail-Version: 0.76.8.0 X-Enigmail-Supports: pgp-inline, pgp-mime 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 RPost wrote: > IBM doesn't build anything without creating extensive architecture and > design documents. That may be true, but IBM didn't create Cloudscape, they acquired the technology. http://incubator.apache.org/derby/#Derby+History The Cloudscape development model has always been light on design documents, the design was intended to be captured in the code, its javadoc and general comments in the code. Functional specifications were written and they are all reflected in the user documentation. > Did IBM donate their cloudscape architecture and design documents to Apache? > > If not, I suggest that we ask them to donate these documents. Since IBM may > have an internal ongoing cloudscape project these documents may need to be > vetted first. > > Who could make this request? You just did :-) I'll try and find some time to look to see if anything is available and useful, however we have been busy donating the code, and then the tests and now more code for a new network client. My guess is that there is nothing that exists that would help people understand an overall view of the system, they may be some focussed papers on certain "edge" areas. Of course any of the IBM developers on the list with Cloudscape experience are always willing to answer design or code questions, and I like the ideas that shahbaz chaudhary proposes in another e-mail. Dan. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFB7q18Iv0S4qsbfuQRAgdzAJ91AT0ArhkG2qLmAOllrHNyYFG4egCgrrHW oQDPvWOAQOhow5/259Ui4Gw= =fM+z -----END PGP SIGNATURE-----