> You are talking about a primary-partition approach. The > literature tells > you to shut down members in a non-primary partitions. It is simple to > implement, all right. But it reduces overall availability of a > distributed system, that's why there are many approaches > beyond primary > partition in research. But regardless of whether we want to have > progress or shutdown on a partition, we need to present to the user a > choice. E.g. shut down, continue and merge later etc. This way we can > implement both approaches.
Yes, I think we are speaking exactly about the same thing: pluggable policy to let the application/user choose which is best for its app and if the network partition is critical for him or not. The primiary partition was just an example. Cheers, sacha ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
