Load balancing is achieved by the client (wiis.dll for example) being told that there are more than one Witango server available to answer requests. The client actually passes the user's request (GET or POST) to the server which in turn determines which TAFs, or TCFs it needs to run. It first checks its local memory cache for the files, and if not present, it requests the files to be sent by the client. Therefore it is true to consider that the web server, which contains the Witango client, is where the TAFs are considered 'local', and are sent from there to the Witango servers (or services).
In my setup, my two Witango servers are distinctly separate from web serving and database duties. It's also nice because you can do the reverse where more than one web server interacts with one Witango server. Note that when purging the cache (<@PURGECACHE>), it must be done on all services, or you will have out of sync applications. Hope that helps some. Robert -----Original Message----- From: Dave Machin [mailto:[EMAIL PROTECTED] Sent: Thursday, December 11, 2003 11:21 AM To: [EMAIL PROTECTED] Subject: Witango-Talk: Load Balancing Question I set up a test of load balancing between 2 WiTango servers yesterday, and found something I didn't expect. I have server A and server B - the actual .taf files are only on server A. However, when requests were handled by server B it didn't complain that the .taf files were unavailable locally. Does server B load the .taf files from server A? If the files were available on server B would it load it's own local copies? Dave Machin E-Mail. [EMAIL PROTECTED] Tel. 805.614.0123 x 30 Address: 3130 Skyway Drive #702 Santa Maria, CA 93455________________________________________________TOUNUBCRBE G t htp//wwwiano.ommallstta ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
