The problem you described below would not occur if you set the server on
the old address to access the datasource on the new address. Two sites
yes, but only one datasource.
> > Couldn't you just point the DSN on the access side to the SQL
> > db until the
> > change takes place?
>
>
> I've got a similar problem.
>
>
> A site is in on a server at IP address 123.0.0.10 (for example).
>
> You move the site to a different server (at the same host or not - doesn't
> make a difference) on IP 218.03.10.50
>
> You alter the DNS entries.
>
> Users connect to the Internet via ISPa. ISPa caches domain names so that it
> resolves to 123.0.0.10 until the TTL kicks in (cognoscenti - is this how it
> works?). Those users hit the site and add / modify / delete data to the
> database on 123.0.0.10.
>
> Other users connect to the Inter via ISPb. ISPb refreshes their domain name
> cache earlier. Their users hit the site at 218.03.10.50 and add / modify /
> delete data to the database on that server.
>
>
> End result - Host1 has a database with some new entries. Host2 has a
> database with some new entries.
>
> Someone (ie the developer) has to go and mop up the differences and compile
> them into the database on Host2.
>
>
> Q: How can you prevent this situation arising without taking the site
> completely offline until ISPb has updated their domain name cache?
>
>
>
> Anwsers on a postcard...
>
> --
> Aidan Whitehall <[EMAIL PROTECTED]>
> Netshopper UK Ltd
> Advanced Web Solutions & Services
>
> http://www.netshopperuk.com/
> Telephone +44 (01744) 648650
> Fax +44 (01744) 648651
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
