Further bonus: the "GUI project" need only have a database connection to one of the databases to control things. No need for ANYTHING else.
After fleshing it out a little, that's a pretty slick approach.
You miss the point, sorry.
This "make GUI easy to write" approach leads to one major problem. When a central server in the cluster dies and the communication path's need to be redirected and the utility needs to contact all the remaining servers because they're not doing the big group chat always, but now their regular communication path is disrupted ... your GUI (the only thing wannabe-DBA's know) becomes useless and the whole plan with failover and backup systems falls apart.
Jan
-- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== [EMAIL PROTECTED] #
---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
