Hey,
I found this in the taglib file:
=====================
Provide access to CFML application scope. in CF5 and earlier, applications
must have a name. Neo supports this behavior by prefixing the application
name onto the variable name. In addition, neo allows you to have an
un-named
application that maps directly to the ServletContext namespace, allowing
sharing of existing variables.
Either way, java can share variables with a legacy cf application by
prepending
the application name onto the servlet context key name. For example, if a
cf application is called "myapp", then in java/jsp you can get
variables like so:
<code> application.getAttribute("myapp.variableName"); <;/code>
Defines scoping for a ColdFusion application, enables or disables storing
client variables, and specifies a client variable storage mechanism. By
default,
client variables are disabled. Also, enables session variables and sets
timeouts
for session and application variables. Session and application
variables are
stored in memory.
=====================
I didn't previously know this, but it seems to be quite handy.
especially the unnamed applications cope which will share variables on
the page (if I read it right).
Seems cool to me :)
Jesse
..
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
