Hi, Dan. This looks very appealing. The one area I'm a little
uncertain about is with the messages that are common across client and
server. If the engine code doesn't use the shared mechanism to load
messages (where the algorithm is look in the shared message bundle
first, then look in your local message bundle), then these messages will
be duplicated between engine and client (sharing the same SQL State).
Alternately I could duplicate the code to look in the shared area first,
but if anything that seems worse.
I guess copying messages (IMHO temporarily) isn't too bad, especially if
they're old, established messages. Any comments?
David
Daniel John Debrunner wrote:
Kathey Marsden wrote:
David W. Van Couvering wrote:
I was wondering if in the meantime I can unblock those who are waiting
for me by checking in the code sharing framework *without* the
classloader work. This would be with the solemn promise to submit the
classloader work soon thereafter, and definitely before the next patch.
I am not comfortable having a regression like that committed, especially
one that has been so tricky to fix.
For things that need to go in now, I prefer the duplicate now and
cleanup later method that Francois suggests.
For new shared code used by the client it could be added to the shared
package while the engine continues to use its current code.
Dan.
begin:vcard
fn:David W Van Couvering
n:Van Couvering;David W
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard
