[FX.php List] GET vs. POST in a web app

[Jason LEWIS]

A question for future lurkers, what would be wrong with keeping the old
server running the WPE as a third server?

>>> Bob Patin <bob at patin.com> 05/07/2007 3:37 PM >>>
Erik,

I think you're on to something, but I'm not sure I grasp it yet:

right now, in the admin console, WPE connects to an IP, but it could  
just have easily been the server's subdomain, which I've already got  
set up.

So what I would do is go into server_data.php and change that IP to  
point to the NEW WPE, and start using it immediately. However, I'd  
still have to kill the existing WPE before the new one will connect.

Am I missing something here? Let me know; I'm not sure what you're  
suggesting when you say that WPE goes to just one DNS record. But I'm 

listening! :)

Thanks,

Bob


On May 7, 2007, at 4:18 PM, Erik Andreas Cayré wrote:

> Yes, my comment was based on Kevin apparently not knowing it's  
> possible that way around...
>
> BTW: if you're not in a hurry, I have a suggestion:
> First arrange to have all connections to the WPE go via just one  
> DNS record (eg. fms.longtermsolutions.com TTL 300)
> That could take some time, but no site will be down even for a  
> minute, while you do this...
> When done, do your switch, and only that one DNS record needs to be 

> updated for all DBconnections to jump on the new server!
>
> I know this could be a pain if there are heaps of customersites,  
> but it's good investment. Next time you'll just smile and be done  
> with it real quick!
>