Hi Bill, > <@ASSIGN SCOPE="domain" NAME="variableTimeout" VALUE ="0">
For version 5.5, it now throws an error "-609. You may not set this configuration variable in the specified scope." Such is life, eh? > -----Original Message----- > From: William M Conlon [mailto:[EMAIL PROTECTED] > Sent: Friday, August 25, 2006 10:40 AM > To: [email protected] > Subject: Re: Witango-Talk: VariableTimeout auto assign? > > I think this would be a useful construct: > > <@ASSIGN SCOPE="domain" NAME="variableTimeoutTrigger" VALUE > ="init_domain.taf"> > > .... > > <@! re-initialize > > <@ASSIGN SCOPE="domain" NAME="variableTimeout" VALUE ="0"> > > So being able to timeout a scope, and do something with the trigger > (trigger doesn't fire in 5) would be a nice to have. > > On Aug 25, 2006, at 9:34 AM, Scott Cadillac wrote: > > > Thank you Dan, Stefan and Robert, > > > > Although I was aware of some behavior change for > VariableTimeout in > > recent versions (like some scopes not expiring?), I was still > > assuming that the VariableTimeout variable would still be present. > > > > I'm maintaining a system for somebody that works very similar to > > what you describe Robert, but the check variable the code was > > calling was the VariableTimeout one - because at some point in the > > past VariableTimeout was a reasonably dependable status check. So > > that code was constantly updating the Domain scope vars with each > > request. > > > > Oh well, I fixed that now. > > > > Thank you guys. > > > > Scott Cadillac, > > Email: [EMAIL PROTECTED] > > http://scott.cadillac.bz > > > > > >> -----Original Message----- > >> From: Robert Garcia [mailto:[EMAIL PROTECTED] > >> Sent: Friday, August 25, 2006 10:23 AM > >> To: [email protected] > >> Subject: Re: Witango-Talk: VariableTimeout auto assign? > >> > >> They used to, in 5.0, and with 5.0 we built our strategies > around it. > >> > >> I have never been comfortable, with ASSUMING a domain var is > >> populated correctly, so we tested heavily the process of > >> checking the > >> vars on each execution, which was so fast, it was almost > >> immeasurable. So from the time forward, with witango, we have a > >> policy in code, that on each execution, a process verifies that our > >> domain objects are initialized. Even though they are called > >> on server > >> startup. We don't necessarily check each domain var, but if I > >> know my > >> initialization method, sets many at once, we may just check one, or > >> check the object status, that created all of them, all of > our domain > >> vars are managed in TCFs. > >> > >> -- > >> > >> 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 Aug 25, 2006, at 8:53 AM, Dan Stein wrote: > >> > >>> I thought the domain scope variables along with custom scope > >>> persist unless > >>> the server is restarted I did not think they timed out. > >>> > >>> -- > >>> Dan Stein > >>> FileMaker 7 Certified Developer > >>> Digital Software Solutions > >>> 799 Evergreen Circle > >>> Telford PA 18969 > >>> Land: 215-799-0192 > >>> Cell: 610-256-2843 > >>> Fax 413-410-9682 > >>> FMP, WiTango, EDI,SQL 2000, MySQL, CWP > >>> [EMAIL PROTECTED] > >>> www.dss-db.com > >>> > >>> > >>> "It's very hard to grow, because it's difficult to let go of > >>> models of > >>> ourselves in which we've invested so heavily." > >>> > >>> > >>>> From: Scott Cadillac <[EMAIL PROTECTED]> > >>>> Reply-To: "[email protected]" <[email protected]> > >>>> Date: Fri, 25 Aug 2006 09:20:00 -0600 > >>>> To: "'[email protected]'" <[email protected]> > >>>> Subject: Witango-Talk: VariableTimeout auto assign? > >>>> > >>>> Hi Folks, > >>>> > >>>> I apologize that I'm not staying as up to date as some of > >> you with > >>>> Witango > >>>> programming, but could someone correct me if I’m wrong, but > >>>> shouldn't a > >>>> VariableTimeout variable be automatically assigned to each > >>>> variable scope? > >>>> > >>>> I have several sets of domain scope variables (in a multi-domain > >>>> system using > >>>> a single set of TAF files), and I noticed that some of the domain > >>>> scopes don't > >>>> have a VariableTimeout variable. > >>>> > >>>> Shouldn't there automatically be one when any domain scope var is > >>>> assigned? Or > >>>> have I totally lost my marbles? > >>>> > >>>> The documentation doesn't explicitly say this, but is > >> implied with > >>>> "The system > >>>> scope version of this configuration variable determines the > >>>> default period, in > >>>> minutes, after which domain and user variables expire." > >>>> > >>>> Running 5.5.009 Liquorice (Win32) on Windows 2003. > >>>> > >>>> Calling @@Domain$variableTimeout returns an empty value, and is > >>>> not in the > >>>> <@VARNAMES SCOPE=domain> list. > >>>> > >>>> Thank you in advance. > >>>> > >>>> Scott Cadillac, > >>>> Email: [EMAIL PROTECTED] > >>>> http://scott.cadillac.bz > >>>> > >>>> > >>>> > >> > _____________________________________________________________________ > >>>> ___ > >>>> 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 > > Bill > > William M. Conlon, P.E., Ph.D. > To the Point > 345 California Avenue Suite 2 > Palo Alto, CA 94306 > vox: 650.327.2175 (direct) > fax: 650.329.8335 > mobile: 650.906.9929 > e-mail: mailto:[EMAIL PROTECTED] > web: http://www.tothept.com > > ______________________________________________________________ > __________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
