The only thing I would add to that, is that if there is an app, like
an upload app that takes large objects, or a taf with an external
process that may take some time, a longer timeout may be necessary.
--
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
rgar...@bighead.net - rgar...@eventpix.com
http://bighead.net/ - http://eventpix.com/
On Feb 18, 2009, at 12:14 PM, Scott Cadillac wrote:
Hi Ted,
A long webserver timeout value is most often pointless (if the
server is giving no response at all), because a browser will likely
timeout before the webserver does.
Hope that helps.
Scott,
On Feb-18-2009, at 3:21 PM, Ted Wolfley wrote:
Hi,
We are trying to troubleshoot a hanging Witango server (windows
2003 web edition, Witango 5.0 server, IIS 6.0) and we noticed that
the IIS connection timeout had been increased to 600 seconds
(default 120 seconds). Is 10 minutes to long for a connection
timeout? We are considering lowering it the default value.
Ted Wolfley
Lead Internet and Database Programmer
The Ogden Group of Rochester
phone: (585) 321 1060 x23
fax: (585) 321 0043
t...@ogdengroup.com
www.ogdengroup.com
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
