Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 36262 invoked from network); 4 Apr 2006 19:19:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Apr 2006 19:19:33 -0000 Received: (qmail 6012 invoked by uid 500); 4 Apr 2006 19:19:32 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 5984 invoked by uid 500); 4 Apr 2006 19:19:32 -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 5975 invoked by uid 99); 4 Apr 2006 19:19:32 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Apr 2006 12:19:32 -0700 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.146] (HELO e6.ny.us.ibm.com) (32.97.182.146) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Apr 2006 12:19:31 -0700 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e6.ny.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k34JIuro003458 for ; Tue, 4 Apr 2006 15:18:56 -0400 Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay02.pok.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k34JIkqj232510 for ; Tue, 4 Apr 2006 15:18:46 -0400 Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.12.11/8.13.3) with ESMTP id k34JIkuE004716 for ; Tue, 4 Apr 2006 15:18:46 -0400 Received: from [127.0.0.1] (sig-9-48-120-231.mts.ibm.com [9.48.120.231]) by d01av04.pok.ibm.com (8.12.11/8.12.11) with ESMTP id k34JIglm004391 for ; Tue, 4 Apr 2006 15:18:45 -0400 Message-ID: <4432C682.4040904@Sourcery.Org> Date: Tue, 04 Apr 2006 12:18:26 -0700 From: Satheesh Bandaram User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: Putting all messages in messages.properties? References: <4432BE25.50901@sun.com> In-Reply-To: <4432BE25.50901@sun.com> X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 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: > The potential drawback is that the client-specific messages are now in > engine-side properties files, which can increase the overall footprint > of derby.jar. My estimate is there will be no more than 200 messages > (MAX) that are client-specific, and possibly quite fewer -- I am > finding many opportunities for reuse of existing messages. How about client footprint? If we have a single message file that included all server and client messages, wouldn't that increase client footprint a lot? Potentially there could be multiple copies of the message files in CLASSPATH to support different languages? derbyLocale_fr, for example, seems to be 71K in size. Satheesh > Thoughts on this are much appreciated. > > David > > >