That seams like an awesome suggestion Danie, i think this is by far better way. 1 problem with this how-ever, i have no idea on how to go about doing all this. Are you able to toss me a few links my way to read up on this. Whats the time frame we looking here to do all this ? and is this all basicly MYSQL based ? not apache at all ? does it require any special license to do it ?
cheers rob On Sat, Jun 21, 2008 at 9:45 AM, Danie Qian <[EMAIL PROTECTED]> wrote: > In your situation, why dont you do it this way: > location1: 4 sites <-> mysql server1, as a master for these 4 local > sites and replicate slave for the 2 sites in the other location. > location2: 2 sites <-> mysql server2, as a master for these 2 local > sites and replicate slave for the 4 sites in the other location > not only this will be more efficient but also it will be more reliable as > you have sort of a real time backup db server. > > ----- Original Message ----- > *From:* Rob <[EMAIL PROTECTED]> > *To:* users@httpd.apache.org ; Danie Qian <[EMAIL PROTECTED]> > *Sent:* Friday, June 20, 2008 5:26 PM > *Subject:* Re: [EMAIL PROTECTED] MYSQL Domain ? > > To explain abit more about my situation, > > I have 6 joomla sites, 4 on one server 2 on another, with more to follow. > What im needing to do is setup a simple form for people to fill out. This > basicly will inject the database of each joomla site with the information > from the form into them. The problem is that the servers are in two sperate > locations so i presumed this would be a good way to connect to the databases > from mulitlple locations. > > Danie, it is possible to have sql running on localhost and over a domain at > the same time ? > > is any one able to point me to some reading material or walkthrough so i > could get a better idea on what needs to be done ? > > cheers > > rob > > On Sat, Jun 21, 2008 at 9:19 AM, Danie Qian <[EMAIL PROTECTED]> > wrote: > >> it is mysql.domainname.com:3306 you should connect to. I recomment you >> keep a local database for each of your location, local i mean on the same >> network. mysql connection from one location to another in the backend causes >> performance issue. you might consider replicating the same db all across >> your different locations. >> >> ----- Original Message ----- >> *From:* Doug Harvey <[EMAIL PROTECTED]> >> *To:* users@httpd.apache.org >> *Sent:* Friday, June 20, 2008 5:17 PM >> *Subject:* RE: [EMAIL PROTECTED] MYSQL Domain ? >> >> Rob. I would think that you would want to use a port number instead of a >> domain name. I think the port number is 3310, so you would have someone >> connect by going to: domainname.com:3310 >> >> Doug >> >> >> ------------------------------ >> *From:* Rob [mailto:[EMAIL PROTECTED] >> *Sent:* Friday, June 20, 2008 2:01 PM >> *To:* users@httpd.apache.org >> *Subject:* [EMAIL PROTECTED] MYSQL Domain ? >> >> Hey there, >> >> wondering if some one could point me on the right direction. I have no >> idea what its actually called but i want to asign my MYSQL to a domain name. >> >> >> So instead of using local host they can use mysql.domainname.com >> >> Basically want this to make my database accessible to our other servers >> which are hosted at all diffrent places around the world. >> >> Could any one give me a brief idea on how this is done ? and the pro's and >> cons of it. >> >> I did trying searching for it but seams i dont actually know whats its >> properly called i came up with very little. I thinking this is done in >> apache ? im just guessing here >> >> thanks, >> >> rob >> >> >
