HI Brett,
>I'm heading down this path at the moment... One question... iMS doesn't
>have an application.cfm template as part of the standard implementation so
>I was just wondering what parameters you are using for <cfapplication> tag
>such as CLIENTMANAGEMENT, SETCLIENTCOOKIES, SESSIONMANAGEMENT,
>SESSIONTIMEOUT, APPLICATIONTIMEOUT, when all we are really trying to do is
>enable application variables...
Considering the context that the CF templates are running in I don't think
you will have much need for client or session variables, there is only one
user! :-) We run with a standard, default, set of params for the
cfapplication tag, ie., we specify the application name only and nothing
else (everything defaults to "off") and use the timeout specified in the
CFadministrator, whatever that might be as the thing never ever gets a
chance to time out :-)
In general to this thread we do use the earlier template to stop bad stuff
as quickly as possible and not get as far as the rcpt.cfm template and we
use an application scope structure to keep all the banned IPs in so the
performance hit is minimal. It works well.
--
Yours,
Kym
==^======================================================================
This list server is Powered by iMS
"The Swiss Army Knife of Mail Servers"
--------------------------------------
To leave this list please complete the form at
http://www.coolfusion.com/iMSSupport.cfm
Need an iMS Developer license? Sign up for a free license here:
http://www.coolfusion.com/iMSDevelopers.cfm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
Note: You are subscribed as [email protected]
==^======================================================================
