You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by Apache Wiki <wi...@apache.org> on 2005/10/06 12:18:58 UTC

[Db-derby Wiki] Update of "ListOfSharedComponent" by TomohitoNakayama

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

------------------------------------------------------------------------------
  
   * Don't we need to think more deeply about each of these functionalities ? ('''TMNK''')
     Same answer as above, I think for the basics I am describing here we have enough information.  Decisions about programming paradigms, dependency injection, interface definition, etc., is out of scope for what I'm proposing here.  I think '''what''' is being shared is really not relevant for what we're trying to address with these guidelines.  All that said, perhaps I'm just missing something basic.  If you can provide a specific example of where an issue can arise with the guidelines I am proposing, that would be very helpful.  I am concerned that we could spend a long time analyzing all the different '''potential''' areas where code can be shared, and I'm having trouble seeing the value in doing this for what I'm proposing. ('''DVC''')
+     I think the points at issue was different between you and me . You was just told about versioning , and I told about component itself. [[BR]]I propose to consider about component itself , apart from versioning issue . I think it is needed to make well formed component . (Well, started at ["JDBC error messages and SQL States"] already :).)('''TMNK''')