Hi, Kathey. I have seen in the code and from various emails the concern
of "client bloat." I don't have the background so I'm sure I'm missing
something.
I can understand wanting to keep the code base small for J2ME, but my
understanding is that doesn't involve client/server. What's the need to
keep the client small since it won't be found in J2ME environments?
Thanks,
David
Kathey Marsden wrote:
TomohitoNakayama wrote:
Then, I propose next :
It is subject of voting to create new shared component . New
shared component require passing the vote .
+1
I too am concerned with the impact of creating shared components
especially with regard to potential client bloat and backward
compatibility risks. I think the code submission for any new shared
component should require a vote. I also think that it would be good to
componentize things in place in client or server before making them a
shared component. For example, for DRDA there is a fair amount of work
to do to extract the sharable parts of DRDA processing from either
server or client. First the code work for untangling the component
could be done in place for either server or client and then once
complete, moved to shared component status.
Kathey
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
