Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 99504 invoked from network); 23 Nov 2005 16:52:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Nov 2005 16:52:17 -0000 Received: (qmail 88935 invoked by uid 500); 23 Nov 2005 16:52:16 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 88899 invoked by uid 500); 23 Nov 2005 16:52:15 -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: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 88888 invoked by uid 99); 23 Nov 2005 16:52:15 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Nov 2005 08:52:15 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [32.97.182.141] (HELO e1.ny.us.ibm.com) (32.97.182.141) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Nov 2005 08:53:47 -0800 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e1.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id jANGprUt018687 for ; Wed, 23 Nov 2005 11:51:53 -0500 Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay02.pok.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id jANGprkE108166 for ; Wed, 23 Nov 2005 11:51:53 -0500 Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.12.11/8.13.3) with ESMTP id jANGpreW005224 for ; Wed, 23 Nov 2005 11:51:53 -0500 Received: from [127.0.0.1] (sig-9-48-126-103.mts.ibm.com [9.48.126.103]) by d01av01.pok.ibm.com (8.12.11/8.12.11) with ESMTP id jANGpqgq005068 for ; Wed, 23 Nov 2005 11:51:53 -0500 Message-ID: <43849E28.7020307@debrunners.com> Date: Wed, 23 Nov 2005 08:51:52 -0800 From: Daniel John Debrunner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: de, en-us, en MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: Backward compatibility of DataSource implementations References: <43839F13.2060206@sun.com> <4384392C.1020204@sun.com> <20051123095422.GE15000@atum01.norway.sun.com> <43849C5D.9080700@sun.com> In-Reply-To: <43849C5D.9080700@sun.com> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N David W. Van Couvering wrote: > Hm, I'm not sure if I am interested in venturing into these waters. The > email I sent was about making sure I understaood how things are done > today: DataSource implementations implement Serializable and define > compatibility requirements in the form I described. > > I think the ideas of using Referenceable or writing our own custom > serialization code are interesting, but it's not my itch to scratch > right now (unless it's required as part of solving the itch I have to > provide a custom classloader). The embedded Derby DataSource implementations do implement Referenceable, that itch has been scratched. The one exception is EmbeddedSimpleDataSource, which is designed to work with J2ME (and J2SE), where Referenceable is not available. Dan.