Pierre van Rooden wrote:
> 
> org.mmbase.storage.change:

org.mmbase.storage.share, you mean? I'm still not sure that this would accurately 
describe the
thing. I hardly thing that 'share' does describe it very clear. 'Changes' are 
essential but it's
only about informing about changes. Actually the notion of 'casting' is more to the 
point. 

org.mmbase.storage.changecasting?
It's about broadcasting information about changes.

org.mmbase.storage.changes?
I feel that the plural somehow would indicate that this is not a
package wich deals with changing storage or so.

org.mmbase.storage.broadcast?
Since 'casting' is programmatic term too, perhaps 'cast' can be confusing, but still 
beter then
'change' or 'shared' I think:

org.mmbase.storage.casting?


> Accept the new multicast/unicast code: 
>  [X] +1 (YES)

 
> Moving the code to org.mmbase.storage .shared :

>  [X] -1 (NO), because :

I do not think that 'shared' is clear, since it can mean a lot. I would probably read 
is as a kind
of synonym for 'util': shared code that can be used in a lot of places. I think that 
if we are to
use a new package name we can as well try to go for something really informative.

I'm +1 for moving it somewhere under org.mmbase.storage though.


 Michiel



-- 
Michiel Meeuwissen                  mihxil'
Mediacentrum 140 H'sum                [] ()
+31 (0)35 6772979         nl_NL eo_XX en_US




Reply via email to