> I think that if you want to change cfapp timeout you
> have to wait until previously set cfapp timeout expires
>
> That doesn't make sense, does it?
> When I have wanted to change cfapp timeout it's
> just been easier to start/stop - it seems (anecdotally)
> that cfapp timeout can't be changed just by rewriting the
> value in the application.cfm script.
>
> Is cfapplication.timeout an addressable value in memory?
>
> It seems like I was just playing with this yesterday - maybe it
> was sessiontimeout, which does respond quickly to script
> changes - which makes sense as it is not a value read or
> useful until a session starts. application timeout seems to
> persist regardless of whether a new session has started.
> Will have to experiment more when time permits.
There's no interface for changing the application timeout by manipulating a
variable in memory.
If you change the value specified in the CFAPPLICATION tag's
APPLICATIONTIMEOUT attribute, it seems, in my informal testing, to override
the previously specified APPLICATIONTIMEOUT value. I created an application,
set the CFAPPLICATION tag's APPLICATIONTIMEOUT attribute for one minute, ran
a script within the application, then reset the timeout for five minutes,
reran the script before the minute had expired, then waited three minutes.
The application hadn't expired. I reversed the process, and the application
expired before five minutes were up.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
