Hi All, As part of writing the conformance tests for the cluster info API, I came across what seems to be some weirdness...
ClusterEvent: This doesn't seem to represent an event very well, as once the event object is orphaned from the method it was supplied through it's impossible to tell what the event is. I'd like to add a Type getType() method, where Type is an inner static enum type inside ClusterEvent that contains the set of possible event types. ClusterInfo: getUniversallyUniqueClientID() - would be nice if this returned a java.util.UUID. I seem to remember this being brought up in conversation before so there may be some technical reason why this can't be done. getNodesWithObject(s): there seem to be too many of these methods. Would be nice if we could reduce this to two, or even one ideally. My vote would be to just have the Collection taking one... ClusterListener: If we add a getType method to the ClusterEvent interface, do we need to have four different methods here? Seems to me that having one method would also allow us to more easily expand the set of events reported to the listeners. CluserNode: Could we consolidate getIp and getHostname in to a single InetAddress getAddress() method? ClusterTopology: Could we just scrap this class and get ClusterInfo to return a Set<ClusterNode>... what purpose does this type really serve? Any and all thoughts are welcome... Chris _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
