I believe you are speaking of the variabletimeout in the user scope. That is, once a user logins in and you assign a user scoped variable that allows Witango to maintain the fact that they are logged in, that login closes after 30 minutes (the default).
For a server wide setting change, edit the Witango.ini file: VARIABLETIMEOUT=minutes (2 hours would be 120) For something less permanent (recommended), when you login a user also: <@ASSIGN user$variabletimeout 120> These commands accomplish the same task of allowing the user's login to persist over longer (or shorter) periods of inactivity, one is simply specific to each user and the other system wide. Hope that helps. Robert -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, April 15, 2004 4:04 PM To: [EMAIL PROTECTED] Subject: RE: Witango-Talk: data sources ROBERT, I'VE SEEN YOUR POSTS A LOT ON WITANGO; I, TOO, USE WIN 2K ADV SERVER AND WITANGO 5.0 SERVER. THERE ARE TIMEOUT ISSUES WHICH MY CLIENT IS CONCERNED ABOUT. THERE IS THE WITANGO DATASOURCELIFE TIMEOUT WHICH I CAN SET TO A LARGE NUMBER, BUT THERE MUST BE OTHER TIMEOUT'S AFFECTING THE CONNECTION. MY CLIENTS DO NOT WANT TO HAVE A TIMEOUT OR HAVE ONE BE ABOUT 2 HOURS. DO YOU HAVE ANY KNOWLEDGE OF THE TIMEOUTS ON A WIN 2K ADV SERVER RUNNING SQL SERVER 2000 SP3 AND IIS V5? TOM ROBERTS HTTP://ORGANIZE-IT.COM ---- Original message ---- >Date: Wed, 14 Apr 2004 15:39:10 -0400 >From: "Robert Shubert" <[EMAIL PROTECTED]> >Subject: RE: Witango-Talk: data sources >To: <[EMAIL PROTECTED]> > >You are correct that it opens new connections when all existing >connections are busy. The trick is defining 'busy'. It can be the case, >due to the internal threading of Witango, that more or less connections >will be opened then you might guess. For the most part, a constantly hit >site will always have 1 open connection. As simultaneity increases so >will the number of connections. You can spot problems with databases by >seeing if the number of connections equals the number of allowable >threads, or is generally very high. Even my busiest sites typically have >only 4-5 connections open. > >In the past I've advocated lower timeouts to keep the connection pool to >a minimum and to often refresh connections. I have recently, however, >found that database connections are more reliable with the newer MDAC >drivers, and now support a 15 minute timer. > >My systems are all Win2k, W5-065 and MSSQL2K > >Robert > > > >-----Original Message----- >From: Alan Wolfe [mailto:[EMAIL PROTECTED] >Sent: Wednesday, April 14, 2004 1:10 PM >To: [EMAIL PROTECTED] >Subject: Witango-Talk: data sources > >hello, > >I was wondering, when you do a <@DATASOURCESTATUS> and it lists >different >data sources along with the user ref they were spawned under (right?), i >see >multiple datasources but not a datasource for each user ref who used >that >datasource. Meaning...in the course of the day if we have 150 users who >deffinately accessed one of the databases, there arent 150 open >datasources >of that database, but there might be anywhere between 5 and 10 of em >open. > >what im wondering is why sometimes will it open a new data source and >other >times for a person and other times it wont? > >Does it only open a new data source when all current data sources from >the >requested source are busy? Or is there some other rule? > >Just trying to better understand. > >Thank you! >Alan > >_______________________________________________________________________ _ >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 ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
