Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Tue, 20 Jun 2006 13:36:46 -0700
From: Rick Hillegas <Richard.Hillegas@Sun.COM>
Subject: Re: Driver autoloading and engine booting
In-reply-to: <449854C1.2080706@sbcglobal.net>
Sender: Richard.Hillegas@Sun.COM
To: derby-dev@db.apache.org
Message-id: <44985C5E.9050202@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <44933535.8050801@sun.com> <449336BF.8060300@sun.com>
 <44941956.3050405@sbcglobal.net> <4498226D.3080702@sun.com>
 <4498392B.9010901@sbcglobal.net> <44984C7F.6080701@sun.com>
 <449854C1.2080706@sbcglobal.net>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)

Kathey Marsden wrote:

> Rick Hillegas  and Kathey Marsden wrote:
> [lots of stuff about implementation details that probably should wait 
> a bit]
>
> I think Dan's summary and focus on goals was good:
> Dan said ...
>
>> I think the goal should be to support auto-loading and to ensure
>> applications that perform some setup and then explicitly load the Derby
>> embedded driver continue to work.
>
>
> Another goal would be to minimize the resources used and permissions 
> demanded by Derby when it is auto-loaded but never used.  For example 
> with auto-loading, we would want to make sure that there were no 
> read/write permissions required and memory usage was kept to a minimum.
>
> Kathey
>
>

I think that Kathey's final goal pretty much sums up the concern which 
Suresh raised. Thanks to everyone's patience, it appears we have our 
consensus: this is a serious problem and we need a solution which 
satisfies these goals. So far there's one solution on the table: Olav's 
original proposal to relocate engine booting.

Thanks,
-Rick