Yeah, I was thinking would have to set up two DSNs and have my code
explicitly choose the master for writing. But selecting a slave for
reading should be handled by something that manages DSN connections.
Maybe it shouldn't be witango, but rather an enhanced DB connector (J/
ODBC), so when there are many slaves it's transparent to the
application -- kind of like multiple witango servers.
On Jan 13, 2006, at 9:29 AM, John McGowan wrote:
I was thinking about using my L4 load balancer to handle this type
of stuff, but of course the load balancer can't really tell the
difference between a read and a write. So I was thinking that I
might have to setup two DSN's if I wanted this type of support. one
that would be load balanced, and another that would only go to the
master.
Of course that would require me to do some rewriting or search and
replacing of my existing code.
/John
William M Conlon wrote:
I was reading up on mySQL database replication (master and
slaves), and was curious whether witango had any facilities to
support replicated db clusters. I was thinking something in the
dsconfig.ini, maybe that would specify the master (for writes) and
the slaves (for reads).
Then we could just refer to our DSN and let witango figure out
where to connect.
_____________________________________________________________________
___
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
Bill
William M. Conlon, P.E., Ph.D.
To the Point
345 California Avenue Suite 2
Palo Alto, CA 94306
vox: 650.327.2175 (direct)
fax: 650.329.8335
mobile: 650.906.9929
e-mail: mailto:[EMAIL PROTECTED]
web: http://www.tothept.com
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
