[cfaussie] Re: Kill them all!!!! --- ALL sessions

2006-06-06 Thread Rod Higgins
    sessionTracker = createObject("java", "coldfusion.runtime.SessionTracker");
    // once created maybe something like the cleanUp() function
    // but it depends on how your ending the sessions sessionTracker.cleanUp();

This might send you on the right path 
 
hth
Rod 
On 6/7/06,  <[EMAIL PROTECTED]> wrote:
Thanks guys,Didn't work, although I think I had tried that once before. Thanks foryour help nevertheless.
jeremy
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "cfaussie" group.  To post to this group, send email to cfaussie@googlegroups.com  To unsubscribe from this group, send email to [EMAIL PROTECTED]  For more options, visit this group at http://groups.google.com/group/cfaussie  -~--~~~~--~~--~--~---


[cfaussie] Re: Kill them all!!!! --- ALL sessions

2006-06-06 Thread

Thanks guys,

Didn't work, although I think I had tried that once before. Thanks for
your help nevertheless. 

jeremy


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"cfaussie" group.
To post to this group, send email to cfaussie@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cfaussie
-~--~~~~--~~--~--~---



[cfaussie] Re: Kill them all!!!! --- ALL sessions

2006-06-06 Thread Charlie Arehart

Do you know for sure that your CFSET of the cookies is indeed causing them
to be set as memory-only cookies on the client? That's certainly what you
want to achieve, to make it so that the cookies are not stored on disk for
the default of a very long time. That way, when the browser is closed the
cookie should be lost.

If the CFSET isn't doing it, you could certainly do CFCOOKIE without an
EXPIRES attribute, which makes it create a memory-only cookie.

But here's another issue: are you ensuring that all browser instances are
closed? Depending on what browser's in use, and how multiple browser windows
are opened, it may be that ALL instances of the browser need to be closed.
In Firefox, that's true. In IE, it depends: if you open a new window with
File>New Window, it will share the memory for sessions with its ancestor
window. If you open it with Start>Programs>IE, or by clicking the IE icon in
the quick launch tray, or by executing the IE shortcut any other way, then
that creates an independent instance of IE with its own memory.

Of course, the session continues to exist on the server. The question is
simply how long the client cookie remains in the browser. If the last
instance of a given browser with a given memory-only cookie is closed, then
when a new browser window is opened, it has no previous cookie (CFID or
CFTOKEN) and therefore the server creates a new one and so there's no longer
a connection with that previous session and it will be terminated at the
given session timeout.

/charlie

-Original Message-
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of 
Sent: Tuesday, June 06, 2006 8:49 PM
To: cfaussie
Subject: [cfaussie] Kill them all --- ALL sessions


Howdy people,

I have found a tiny issue with our application. When we close the browser it
doesn't release the application. i.e. the session doesn't seem to clear.

1. Is there a way to totally blow away all sessions when the browser closes.
prefer not to call another page using javascript if we can get away with it.

2. Does Application.cfc have any abilities to cater for this?

3. Any other ideas.

Its becoming serious issue. Below is a little snippet of our Application.cfm
pretty standard stuff.







Jeremy





--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"cfaussie" group.
To post to this group, send email to cfaussie@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cfaussie
-~--~~~~--~~--~--~---



[cfaussie] Re: Kill them all!!!! --- ALL sessions

2006-06-06 Thread Dale Fraser

Yes,

Use this









This is pretty standard I think everyone has this bit of code in
application.cfm

Or like us in OnRequestStart of application.cfc

Regards
Dale Fraser



-Original Message-
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of 
Sent: Wednesday, 7 June 2006 10:49 AM
To: cfaussie
Subject: [cfaussie] Kill them all --- ALL sessions


Howdy people,

I have found a tiny issue with our application. When we close the
browser it doesn't release the application. i.e. the session doesn't
seem to clear.

1. Is there a way to totally blow away all sessions when the browser
closes. prefer not to call another page using javascript if we can get
away with it.

2. Does Application.cfc have any abilities to cater for this?

3. Any other ideas.

Its becoming serious issue. Below is a little snippet of our
Application.cfm pretty standard stuff.







Jeremy




--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"cfaussie" group.
To post to this group, send email to cfaussie@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cfaussie
-~--~~~~--~~--~--~---



[cfaussie] Re: Kill them all!!!! --- ALL sessions

2006-06-06 Thread Haikal Saadh

That's sort of normal for sessions, isn't it? They don't actually expire 
till the a certain timeout elapses _after_ the browser closes. You could 
try tweaking the timeout to be something shorter, just be aware that you 
should allow users ample time to do their thing. (I often have things 
sitting in background tabs for quite a while)

 wrote:
> Howdy people,
> 
> I have found a tiny issue with our application. When we close the
> browser it doesn't release the application. i.e. the session doesn't
> seem to clear.
> 
> 1. Is there a way to totally blow away all sessions when the browser
> closes. prefer not to call another page using javascript if we can get
> away with it.
> 
> 2. Does Application.cfc have any abilities to cater for this?
> 
> 3. Any other ideas.
> 
> Its becoming serious issue. Below is a little snippet of our
> Application.cfm pretty standard stuff.
> 
> name="Validator_2_3_DEV"
>sessionmanagement="yes"
>   setclientcookies = "true"
>   sessiontimeout="#CreateTimeSpan(0,1,0,0)#"
>clientmanagement="true">
> 
> 
> 
> 
> 
> Jeremy
> 
> 
> > 
> 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"cfaussie" group.
To post to this group, send email to cfaussie@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cfaussie
-~--~~~~--~~--~--~---