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 TomohitoNakayama
Date Thu, 29 Sep 2005 12:49:22 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 TomohitoNakayama:
http://wiki.apache.org/db-derby/ListOfSharedComponent

------------------------------------------------------------------------------
  = 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'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 code of "DRDA networking encode/decode " is more and more difficult to share
than "ProductVersionHolder". There would exist subtle but essential difference between Server
and Client in "DRDA networking encode and decode" . On the other hand, there would be not
so much of difference in "ProductVersionHolder". I think different approach is needed for
them . ('''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''')
    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''')
+    I think we need to consider more about what is the components corresponding to each functionalities
, as preparation of sharing the code . Without such preparations, the shared component would
fail to have good structure . ('''TMNK''')
  
+  * Don't we need to think more deeply about each of these functionalities ? ('''TMNK''')
+ 

Mime
View raw message