> you have to be able to cope with the fact that the user may have > altered their registry - adding conflicting entries, removing > others, etc.
Agreed. If rows of a table are independent, which they should be in a well-normalized SQL database, then one can add a column that indicates the data source or date of update or both. This usually gives an intelligent update procedure enough information to decide whether it needs to override the local modification. Simplest approach is "only override an entry if it has the same data source key" though that misses many cases. Having this discussion in the context of mime types, though, may be silly. For mime types, more is almost always better. What's more interesting is other sorts of configuration parameters and collisions in other sorts of locally modified files that don't lend themselves to being loaded into the db. In a Java world, maybe the best approach is to check in a complete dspace distro in Eclipse and then use the configuration control in Eclipse to manage local updates. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
