It does make sense - if the cookies aren't set in the browser, you get a new session with new cookies.
It occurs to me the same is true regardless of which method you are using - Application.cfc or a CFAPPLICATION tag. Is that right Jochem? On 5/23/06, Michael Dinowitz <[EMAIL PROTECTED]> wrote: > I'll have to test that as it sounds logical but doesn't 'feel' right. Your > probably totally correct, but.... > > > Sessions and applications are entirely different beasts here. For both > > the starting point is the part of the manual James referred to. But > > for sessions there is an additional consideration. If the user-agent > > has not made any previous requests for resources on the server, it > > does not have a cookie or URL variable yet. So if the user-agent is > > directed to load 2 resources from the server simultaneously, those 2 > > request will actually be in different sessions. So within a session > > all single-threading is taken care off, but that does not stop a > > user-agent from simultaneously opening multiple sessions. > > > > Jochem > > > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:241201 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
