|
Custom tags are identified by the CF_ prefix. Beyond that, you are free to use any naming convention that fits your development practice. Unique descriptive names make it easy for you and others to find the right tag. For example, the tag name CF_MyTag invokes the file MyTag.cfm
If you are concerned about possible name conflicts when invoking a custom tag or if the application must use a variable to dynamically call a custom tag at runtime, the CFMODULE element provides a solution. See Resolving file name conflicts.
|
|
|
Because custom tags are individual templates, there is no automatic exposure of variables and other data between a custom tag and the calling template. To pass data, you define attributes for the custom tag just as in standard CFML coding.
Data pertaining to the HTTP request or to current application is visible, however. This includes the variables in Form, URL, CGI, Cookies, Server, Application, Session, and Client.
|
|