CALL FOR: moving all shared storage implementations to applications
Called by: Nico Klasens
START OF CALL: 28 april 2005 00:00 END OF CALL: 3 may 2005 00:00
Create a sharedstorage module under applications and store all the implemenations in this module.
Total tally on this call (excluding the caller's vote) : 7*
YEA (8) : Daniel Ockeloen, Rico Jansen, Johannes Verelst, Gerard van Enk, Andre van Toly, Kees Jongenburger, Nico Klasens*, Pierre van Rooden
ABSTAIN (2) : Rob Vermeulen, Michiel Meeuwissen for the 'core' package. NAY (0) :
VETO (0) :
Repackage remaining sources to another package Total tally on this call (excluding the caller's vote) : 6*
YEA (8) : Daniel Ockeloen, Rico Jansen, Johannes Verelst, Gerard van Enk, Andre van Toly, Kees Jongenburger, Nico Klasens*, Michiel Meeuwissen
ABSTAIN (1) : Pierre van Rooden
NAY (1) : Rob Vermeulen
VETO (0) :
No votes, assumed abstained (6): Eduard Witteveen, Jaco de Groot, Marcel Maatkamp, Rob van Maris, Mark Huijser, Ernst Bunders
*) This vote needs a total tally of +3 votes in addition to any in favor vote of the vote's caller.
Call result:
Both votes succeeded.
- An application can be made to move all changeinterface implementations to (excepting the Dummy implementation) .
- The 'core' code (Dummy implementation etc) will be moved to a separate package.
The name of the application and package are determined in another vote.
They are "Clustering" for the application and "org.mmbase.clustering" for the 'core' package.
Implementations are stored in subpackages under org.mmbase.clustering.implementation.
Nico Klasens wrote:
CALL FOR: moving all shared storage implementations to applications
The vote for the jgroups sharedstorage implementation succeeded and can be included in the cvs applications module. This is a vote to propose a name for the module and package name for the new implementation. And more importantly, this vote is for moving current source code from the cvs src module (core) to the new module (applications).
I would like to create a sharedstorage module and commit all the implementations in this module. The implementations will be repackaged:
The current implementations are under org.mmbase.module.core.change
The java source tree will look something like this
org.mmbase.sharedstorage MessageProbe SharedStorage WaitNode org.mmbase.sharedstorage.multicast Multicast MulticastChangesReceiver MulticastChangesSender org.mmbase.sharedstorage.unicast Unicast UnicastChangesReceiver UnicastChangesSender org.mmbase.sharedstorage.jgroup Multicast MulticastChangesReceiver MulticastChangesSender
The main reason for this is to make the clustering facility of mmbase more visible. Now it is hidden inside the core while it is a good selling point for mmbase. It also makes it possible to recommend the jgroup implementation and explain when to use the other ones.
I would also like to repackage the remaining sources in the core. These files are org.mmbase.module.core.MMBaseChangeInterface org.mmbase.module.core.change.MMBaseChangeDummy org.mmbase.storage.util.ChangeManager
The proposed package is: org.mmbase.storage.shared
START OF CALL: 28 april 2005 00:00 END OF CALL: 3 may 2005 00:00
Create a sharedstorage module under applications and store all the implemenations in this module.
[_] +1 (YEA) [_] +0 (ABSTAIN ) [_] -1 (NAY), because : [_] VETO, because:
Repackage remaining sources to org.mmbase.storage.shared
[_] +1 (YEA) [_] +1 (YEA), but in package ________ [_] +0 (ABSTAIN ) [_] -1 (NAY), because : [_] VETO, because:
Nico Klasens _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Anything worth doing is worth overdoing." _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
