Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Knowing when a window is really closing? 1
- Thread starter davem99
- Start date
-
1
- #2
Are you just trying to end a user's session and close any database operations? If so, then you can use the Session_OnEnd in the global.asa file. This file would be stored in the root directory of your website application, but is not mandatory to be there.
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
- Thread starter
- #3
I need to reset a column in my table that is set when they login.
I have code in the Session_OnEnd event that says:
Update mytable set Connected=0 where ID=Session("memberID"
Unfortunately, it seems that this doesn't cut it - perhaps because the memberID session var goes on session end?
I dunno.
I have code in the Session_OnEnd event that says:
Update mytable set Connected=0 where ID=Session("memberID"
Unfortunately, it seems that this doesn't cut it - perhaps because the memberID session var goes on session end?
I dunno.
Session ends after the specified last interation time (set in IIS > site properties > Directory > Configurations > app object - Session timeout) with the server. That means Session_OnEnd fires after a set time when the browser close.
<body onunload="JavaScript:location.href='logout.asp'">
But u can make both happen at once u can call a intermediate ASP page when you are loging out or closing the page. and in this page u can code like this
<% Session.Abandon %>
or any other database logic
this will force the session to end and will fire Session_OnEnd
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
<body onunload="JavaScript:location.href='logout.asp'">
But u can make both happen at once u can call a intermediate ASP page when you are loging out or closing the page. and in this page u can code like this
<% Session.Abandon %>
or any other database logic
this will force the session to end and will fire Session_OnEnd
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
- Thread starter
- #5
Thanks, Brian.
I have a function that pops up an small window and tells the user they're being logged out and it closes.
Unfortunately, it looks like unload fires on refresh or POST so it kicks my user out pretty much whenever they do anything
Any ideas?
thanks!
I have a function that pops up an small window and tells the user they're being logged out and it closes.
Unfortunately, it looks like unload fires on refresh or POST so it kicks my user out pretty much whenever they do anything
Any ideas?
thanks!
Is there anything you can do with window.close()?
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
How 'bout something like this?
<script language="javascript">
var newWindow;
function openNewWindow(URLtoOpen, windowName, windowFeatures) {
newWindow=window.open(URLtoOpen, windowName, windowFeatures);
}
function closeWin () {
if (newWindow != null) {
newWindow.close();
}
}
</script>
<BODY onUnload="closeWin()">
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
<script language="javascript">
var newWindow;
function openNewWindow(URLtoOpen, windowName, windowFeatures) {
newWindow=window.open(URLtoOpen, windowName, windowFeatures);
}
function closeWin () {
if (newWindow != null) {
newWindow.close();
}
}
</script>
<BODY onUnload="closeWin()">
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
- Thread starter
- #8
- Thread starter
- #9
Thanks Brian, I think we posted at the same time above so my comment makes more sense after the previous post!
Here's what I have:
<script LANGUAGE="JavaScript">
<!--
function LogOff()
{
window.open('autologoff.asp', 'Window1', 'resizable,height=130,width=260');
}
//-->
</script>
<body onunload="LogOff();">
Again, all is fine except f5 and POST triggers unload too
Here's what I have:
<script LANGUAGE="JavaScript">
<!--
function LogOff()
{
window.open('autologoff.asp', 'Window1', 'resizable,height=130,width=260');
}
//-->
</script>
<body onunload="LogOff();">
Again, all is fine except f5 and POST triggers unload too
Ok, here is an example that will take care of the refresh and form post. It will determine if the window is being closed via the "X" in the upper right corner or a hyperlink (#2) that has the ClosesWindow set to true.
You can add a location.href in the CheckWindowClosed function.
<html>
<head>
<Script language="javascript">
var ClosesWindow = true;
function CheckWindowClosed() {
// This code only fires when the window is closed when the
alert('Page Closed');
}
</script>
</head>
<body onBeforeUnload="if(ClosesWindow == true){CheckWindowClosed();}" onmouseover="ClosesWindow=false;" onmouseout="ClosesWindow=true;">
<a href="">Does not count as a window close</a> <br>
<a href="" onmousedown="ClosesWindow=true;">Counts as a closed window</a>
</body>
</html>
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
You can add a location.href in the CheckWindowClosed function.
<html>
<head>
<Script language="javascript">
var ClosesWindow = true;
function CheckWindowClosed() {
// This code only fires when the window is closed when the
alert('Page Closed');
}
</script>
</head>
<body onBeforeUnload="if(ClosesWindow == true){CheckWindowClosed();}" onmouseover="ClosesWindow=false;" onmouseout="ClosesWindow=true;">
<a href="">Does not count as a window close</a> <br>
<a href="" onmousedown="ClosesWindow=true;">Counts as a closed window</a>
</body>
</html>
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
- Thread starter
- #11
hmmm...maybe we can capture the screen coordinates and see if the mouse is outside the main window when the "Refresh" is performed. Let me do a little research on this too. I will post back in a few.
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
- Thread starter
- #13
you would think..still lookin'
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
- Thread starter
- #15
OK....I found (but not yet tested) 2 options....
1) This is IE only apparently
function onClose()
{
if ((window.event.clientX<0) && (window.event.clientY<0))
alert("you closed me"
}
...
<body onunload="onClose()">
and
2) Use frames and dump the close logic in a frame that isn't visible so won't be impacted by POST or refresh.....
<html>
<head>
<title>frames example</title>
</head>
<noframes>To be viewed properly, this page requires frames.
</noframes>
<frameset rows="100%, *">
<frame src="dummy.html">
<frame src="leave.jsp">
</frameset>
</html>
<html>
<head>
</head>
<body onunload="leave()">
<!-- body onbeforeunload="leave()" -->here
</body>
</html>
<script language="JavaScript">
function leave() { document.location.href="</script>
still seems like a pain in the &%$ though.....
1) This is IE only apparently
function onClose()
{
if ((window.event.clientX<0) && (window.event.clientY<0))
alert("you closed me"
;}
...
<body onunload="onClose()">
and
2) Use frames and dump the close logic in a frame that isn't visible so won't be impacted by POST or refresh.....
<html>
<head>
<title>frames example</title>
</head>
<noframes>To be viewed properly, this page requires frames.
</noframes>
<frameset rows="100%, *">
<frame src="dummy.html">
<frame src="leave.jsp">
</frameset>
</html>
<html>
<head>
</head>
<body onunload="leave()">
<!-- body onbeforeunload="leave()" -->here
</body>
</html>
<script language="JavaScript">
function leave() { document.location.href="</script>
still seems like a pain in the &%$ though.....
Yeah, I don't think there is a really clean way of doing this, although, I sort of like the frames method as you described.
Did you try posting in the JavaScript forum since this has much to do with JavaScript, more than ASP.
I suppose you could also give the user a confirmation window (then redirect if necessary) and let them decide if they would like to logout. I know that this would be annoying when they click on the refresh button, but in your application, do you anticipate the refresh button will be clicked a lot?
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
Did you try posting in the JavaScript forum since this has much to do with JavaScript, more than ASP.
I suppose you could also give the user a confirmation window (then redirect if necessary) and let them decide if they would like to logout. I know that this would be annoying when they click on the refresh button, but in your application, do you anticipate the refresh button will be clicked a lot?
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
- Thread starter
- #17
Yes - I did post this to the Java peeps too.
The frames are kindof cool approach to the problem but something just keeps bugging me that there HAS to be an easy way!!
The Confirm? would annoy the hell out of my users since OnUnload fires on POST and my app is full of self-POSTing forms.
Thanks again for your help on this!
-dave
The frames are kindof cool approach to the problem but something just keeps bugging me that there HAS to be an easy way!!
The Confirm? would annoy the hell out of my users since OnUnload fires on POST and my app is full of self-POSTing forms.
Thanks again for your help on this!
-dave
Thanks for the star and no problem. Have you considered posting to a separate ASP file and redirecting back after you processed the information? Would this alleviate any issues?
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
- Thread starter
- #19
Cool, hope you find what you need. If I find something I will be sure to post back.
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
regards,
Brian
The problem with doing something right the first time is that nobody appreciates how difficult it was.
- Status
Similar threads
- Locked
- Question
- Locked
- Question