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

[John May]

You have me confused with the "FMSA" term.  FMSA 
is the combination of 3 components - the Web 
Server Module, the WPE and FMS.

You can connect one Web Server Module to multiple 
WPE instances, which can each then be connected 
to one FMS instance each.  However, you cannot 
connect multiple WPE instances to one FMS 
instance.

And, yes, the scenario I describe connecting one 
Web Server Module to multiple WPE instances 
requires some command-line finagling and is not 
officially supported by FMI, but it does work 
flawlessly in our experience.

	- John


>Well, I never was able to get 2 WPEs connected 
>to my FMSA machine, but I gather that John May 
>at Point in Space has a method of doing that 
>using Terminal (John, please correct me if I'm 
>wrong). Not being much of a command-line-savvy 
>person, I didn't pursue it, especially since it 
>was a need that I had only for migrating to the 
>new machine.
>
>I'll be adding another FMSA machine next month, 
>and will get another web server to go with it 
>when I do so; it would be nice to be able to 
>connect any site with any FMSA box, but I'll 
>just keep my FMSA boxes partnered with specific 
>web servers.
>
>Bob Patin
>Longterm Solutions
>bob at longtermsolutions.com
>615-333-6858
>http://www.longtermsolutions.com
>
>   CONTACT US VIA INSTANT MESSAGING:
>      AIM or iChat: longterm1954
>      Yahoo: longterm_solutions
>      MSN: tech at longtermsolutions.com
>      ICQ: 159333060
>
>
>On May 10, 2007, at 11:16 AM, Jason LEWIS wrote:
>
>>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!

-- 

-------------------------------------------------------------------
John May : President                 <http://www.pointinspace.com/>
Point In Space Internet Solutions             jmay at pointinspace.com

        Professional FileMaker Pro, MySQL, Lasso & PHP Hosting