Adobe 38000827 Administration Guide - Page 21

Mappings Mail Server Developing ColdFusion MX, Applications with CFML, web_root

Page 21 highlights

You can specify maximum and default timeout values for session and application variables. Unless you define a timeout value in Application.cfm, application variables expire in two days. Session variables expire when user sessions end. To change these behaviors, enter new default and maximum timeout values on the Memory Variables page of the Administrator. Note: Timeout values that you specify for application variables override the timeout values set in Application.cfm. You can also specify whether to use J2EE session variables. When you enable the J2EE session variables, ColdFusion creates an identifier for each session and does not use the CFToken or CFID cookie value. For more information, see Developing ColdFusion MX Applications with CFML. Mappings page You use the Mappings page of the ColdFusion Administrator to add, update, and delete logical aliases for paths to directories on your server. ColdFusion mappings apply only to pages processed by ColdFusion MX with the cfinclude and cfmodule tags. If you save CFML pages outside of the web_root (or whatever directory is mapped to "/"), you must add a mapping to the location of those files on your server. Assume that the "/" mapping on your server points to C:\CFusionMX\wwwroot, but all your ColdFusion header pages reside in c:\2002\newpages\headers. In order for ColdFusion MX to find your header pages, you must add a mapping in the ColdFusion Administrator that points to c:\2002\newpages\headers (for example, add a mapping for /headers that points to c:\2002\newpages\headers). In the ColdFusion pages located in C:\CFusionMX\wwwroot, you reference these header pages using /headers in your cfinclude and cfmodule tags. Note: ColdFusion mappings are different from web server virtual directories. For information on creating a virtual directory to access a given directory using a URL in your web browser, please consult your web server's documentation. Mail Server page You use the Mail Server page of the ColdFusion Administrator to specify a mail server to send automated e-mail messages. ColdFusion MX supports the Simple Mail Transfer Protocol (SMTP) for sending e-mail messages and the Post Office Protocol (POP) for retrieving e-mail messages from your mail server. To use e-mail messaging in your ColdFusion applications, you must have access to an SMTP server and/or a POP account. The ColdFusion implementation of SMTP mail uses a spooled architecture. This means that when a cfmail tag is processed in an application page, the messages generated might not be sent immediately. If ColdFusion is extremely busy or has a large queue, delivery could occur after some delay. Note: For more information about the cfmail tag, see Developing ColdFusion MX Applications with CFML. Server Settings section 13

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68

Server Settings section
13
You can specify maximum and default timeout values for session and application
variables. Unless you define a timeout value in Application.cfm, application variables
expire in two days. Session variables expire when user sessions end. To change these
behaviors, enter new default and maximum timeout values on the Memory Variables
page of the Administrator.
Note:
Timeout values that you specify for application variables override the timeout values
set in Application.cfm.
You can also specify whether to use J2EE session variables. When you enable the J2EE
session variables, ColdFusion creates an identifier for each session and does not use the
CFToken or CFID cookie value. For more information, see
Developing ColdFusion MX
Applications with CFML
.
Mappings page
You use the Mappings page of the ColdFusion Administrator to add, update, and delete
logical aliases for paths to directories on your server. ColdFusion mappings apply only to
pages processed by ColdFusion MX with the
cfinclude
and
cfmodule
tags. If you save
CFML pages outside of the
web_root
(or whatever directory is mapped to "/"), you must
add a mapping to the location of those files on your server.
Assume that the "/" mapping on your server points to C:\CFusionMX\wwwroot, but all
your ColdFusion header pages reside in c:\2002\newpages\headers. In order for
ColdFusion MX to find your header pages, you must add a mapping in the ColdFusion
Administrator that points to c:\2002\newpages\headers (for example, add a mapping for
/headers that points to c:\2002\newpages\headers). In the ColdFusion pages located in
C:\CFusionMX\wwwroot, you reference these header pages using /headers in your
cfinclude
and
cfmodule
tags.
Note:
ColdFusion mappings are different from web server virtual directories. For
information on creating a virtual directory to access a given directory using a URL in your
web browser, please consult your web server’s documentation.
Mail Server page
You use the Mail Server page of the ColdFusion Administrator to specify a mail server to
send automated e-mail messages. ColdFusion MX supports the Simple Mail Transfer
Protocol (SMTP) for sending e-mail messages and the Post Office Protocol (POP) for
retrieving e-mail messages from your mail server. To use e-mail messaging in your
ColdFusion applications, you must have access to an SMTP server and/or a POP
account.
The ColdFusion implementation of SMTP mail uses a spooled architecture. This means
that when a
cfmail
tag is processed in an application page, the messages generated might
not be sent immediately. If ColdFusion is extremely busy or has a large queue, delivery
could occur after some delay.
Note:
For more information about the
cfmail
tag, see Developing ColdFusion MX
Applications with CFML.