This is technically true, and a great feature, but unfortunately,
especially under load, it rarely works that way. If a witango service
dies, or crashes, this will work, and the witango service should even
restart itself. The problem is, that when witango crashes in
production, it often goes into a state, that still looks to the
witango plugin like it is active, so it still gets requests, but they
don't get fulfilled. You get client errors, or just blank pages. So
you still have to carefully monitor your witango services and don't
expect the plugin to do this correctly.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Oct 7, 2007, at 4:02 PM, Fogelson, Steve wrote:
The more I get into load balancing the more excited I get. I didn't
realize
that the Witango client operates independently of the Witango
server. I did
some testing by killing the Witango service on the server that has
IIS,
Witango client and Witango server running on it and everything
still kept
chugging away. The Witango Client kept distributing jobs to the
other server
and jobs that were already on the other server kept running fine.
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
