Just for my understanding about applicationname and sessions.
If I have a file named /appA/index.cfm with an Application.cfc in the same
folder and this Application.cfc specifies THIS.name="A" in the constructor area
and if I request a page from this directory for the 1st time, onSessionStart
fires and sessioncookies are set with the client.
>From then on, whenever I request a page from the same domain that is preceded
>by this Application.cfc (with THIS.name="A" in the constructor area) the same
>session gets used (until it times out).
An applicationname is merely used to "tag" a set of variables to belong
together.
("What Is A ColdFusion Application?" by Ben Nadel)
Right?
So what happens if I request a page on the same domain but in another folder
(say /appA/appB that has its own Application.cfc in that same folder
(/appA/appB) but this one specifies THIS.name="B" in the constructor area?
I thought: since the Application.cfc specifies another THIS.name,
onsessionstart gets fired, new sessioncookies are sent in the response and as
long as I request pages that are preceded by this Application.cfc I use this
session.
I had a setup like this but found out to my surprise that when I switch from
the 1st to the 2nd scenario (using the application.cfc with THIS.name="B"), the
value for session.sessionId did not change. And all my sessionvariables were
still there.
Why is this?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to
date
Get the Free Trial
http://ad.doubleclick.net/clk;203748912;27390454;j
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:308348
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
