A daemon could forward insert/update requests to a master and all others round-robin and simply pass packets. This is if you have to make it seamless. Would require some work to make one though.
-Mike
From: Jeff Smelser <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: MySQL & Web Clustering... Date: Fri, 18 Jun 2004 11:43:05 -0500
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Friday 18 June 2004 11:05 am, Mike Miller wrote:
> Unless you have a specific need for it, you could save yourself a lot of
> trouble by putting select tables or databases or even clients on each
> server. This also means you don't incur the added overhead of keeping the
> database in sync, creating actions if a master goes down, etc. Then just
> tell client1 to use database5 as their hostname for example. Replication
> requires that updates go to the master, which requires client-side code, or
> an intermediate daemon which analyzes the statement and forwards the
> request.
Daemons? Client side code? Can you explain this please?
mysql handles all the replication. Depending on your setup, client won't know
the difference. Its really all depends on how your replication is gonna be
set up.
- --
SUSHIDO--The way of the Tuna.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA0xuZld4MRA3gEwYRAv1EAKCot3j1j16j892FtrTEea8Brlk0NgCcCKou 9K0QzPH4uFz+TYynwdNpxbY= =a/OR -----END PGP SIGNATURE-----
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
_________________________________________________________________
Free yourself from those irritating pop-up ads with MSn Premium. Get 2months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
