Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 97581 invoked from network); 24 Feb 2006 19:50:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Feb 2006 19:50:12 -0000 Received: (qmail 30970 invoked by uid 500); 24 Feb 2006 19:50:04 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 30855 invoked by uid 500); 24 Feb 2006 19:50:03 -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 30774 invoked by uid 99); 24 Feb 2006 19:50:03 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Feb 2006 11:50:03 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of mcintyre.a@gmail.com designates 64.233.182.193 as permitted sender) Received: from [64.233.182.193] (HELO nproxy.gmail.com) (64.233.182.193) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Feb 2006 11:50:02 -0800 Received: by nproxy.gmail.com with SMTP id o60so335034nfa for ; Fri, 24 Feb 2006 11:49:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=P8FlQRiPgwXkmRKH/KoUKfKxhiS93Sp2rRj2ZeTiOb8NuBX9WB7o6vfr+71Hy7bTsBmQF82PAG+I1eqgq9EzDEbJJxBTpiU7C5/b3qlnSeZBZvnai7NJBGfcml7GcLWMGN2Gz8RnEwOzqPWfmUU2a57hxM3dQ3ie7sdv54tIQC0= Received: by 10.49.21.16 with SMTP id y16mr2887132nfi; Fri, 24 Feb 2006 11:49:40 -0800 (PST) Received: by 10.48.162.20 with HTTP; Fri, 24 Feb 2006 11:49:40 -0800 (PST) Message-ID: <54ac72d70602241149k4daf2e4fw41bf6b80f4b60221@mail.gmail.com> Date: Fri, 24 Feb 2006 11:49:40 -0800 From: "Andrew McIntyre" To: derby-dev@db.apache.org Subject: Re: default ij protocol (was Re: [WWD] review suspended) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <54ac72d70602241019r21243835m87072f683e7bcae1@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 2/24/06, Myrna van Lunteren wrote: > > I wonder - could we leave ij alone, and in run.java add the check for > protocol? That way, we leave all the capabilities of calling ij using the > old scripts exactly as is, yet provide the ease of use of running java -j= ar > derbytools.jar ij with a default protocol? Yes, we could. Although, it seems to me that the behavior wouldn't be any different if we just made it the default in ij itself. The old scripts, for example, would continue to work as-is just as they would before. And, if you were connecting to a database using a non-Derby JDBC driver with a fully qualified URL, again no change in current behavior. And, if the change was in ij, then you get the benefit of the default protocol if you call the class directly as well. andrew