db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "ListOfSharedComponent" by DavidVanCouvering
Date Thu, 29 Sep 2005 11:04:36 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by DavidVanCouvering:
http://wiki.apache.org/db-derby/ListOfSharedComponent

------------------------------------------------------------------------------
  = Shared Component =
  
- These components are discussed as shared component used by ["subsystems of Derby"] .
+ The functionality below are possible areas where code can be shared across ["subsystems
of Derby"] .
  
-    * Internationalization component
+    * Internationalization
-    * JDBC error messages and SQL States component
+    * JDBC error messages and SQL States
-    * DRDA networking encode/decode functionality component
+    * DRDA networking encode/decode functionality
-    * Security encryption/decryption of network traffic, passwords, etc. component
+    * Security encryption/decryption of network traffic, passwords, etc.
+    * Other common functionality between embedded and client JDBC drivers
-    * SanityManager and associated sanity classes component
+    * !SanityManager and associated sanity classes
-    * ProductVersionHolder and associated info classes component
+    * !ProductVersionHolder and associated info classes
-    * Common functionality between embedded and client JDBC drivers component (Is'nt this
ambiguos comparing others in above ? ('''TMNK''')) 
  
  = Question =
-  * Don't we need multiple sharing strategies for those components ? I can't believe we can
share "DRDA networking encode/decode functionality" component as same as "ProductVersionHolder
and associated info classes" component ('''TMNK''')
-  * I think we need to make those component clear enough to consider about . For example,
I think concept of "Internationalization component" is not so clear that we can't discuss
how to share it between subsystems. ('''TMNK''') 
+  * Don't we need multiple sharing strategies for those components ? I can't believe we can
share "DRDA networking encode/decode functionality" component as same as "ProductVersionHolder
and associated info classes" component ('''TMNK''')  I'm not sure what you mean by multiple
sharing strategies, can you explain some more?  ProductVersionHolder would likely go into
the "common" component along with Internationalization, error messages and SQL states, SanityManager,
whereas DRDA networking stuff might belong in its own component.  But I think both of these
can follow the same approach as proposed ('''DVC''')
+  * I think we need to make those component clear enough to consider about . For example,
I think concept of "Internationalization component" is not so clear that we can't discuss
how to share it between subsystems. ('''TMNK''')  I listed these not as components but as
functionality to be compared.  I am not prepared at this time to identify exactly how these
areas of code would be composed into components. These were just ideas for possible areas
of sharing ('''DVC''')
  

Mime
View raw message