새로고침(refresh) 막는법

duraboys 2007. 10. 5. 17:08

2007. 10. 5. 17:08

Detecting Page Refresh

Steven Bey

12.11.2004

Introduction

A common problem that Web Application Developers encounter is how to stop the user from refreshing the page. This is a problem if the previous request to the server was a PostBack, which, for example, inserted the WebForm’s data into a database. The result: duplicate rows in the database. The answer to this problem is that you can’t stop the user from refreshing the page, however there is a way to determine if this event has occurred.

In his article “Build Your ASP.NET Pages on a Richer Bedrock” Dino Esposito outlined a mechanism to detect a page refresh. This method is cumbersome and more complicated than necessary, although the fundamental idea is sound and forms the basis of this solution. Dino’s mechanism uses a counter stored on the page and a session variable to store the previous request’s counter on the server, if the two match then we have a page refresh.

A Simpler Method

Keeping the whole process within a base Page Class ensures that the mechanism is completely encapsulated (and simple to implement) and if we use ViewState we eliminate the need to use an additional hidden field. Also, as we simply want to test if the two storage devices contain the same value, we can use two boolean variables, which further simplifies the process.

The last decision to make is where, in the Page’s lifecycle, should the process take place. As we are using ViewState it would seem logical to perform the operation in the LoadViewState and SaveViewState methods. Using these two methods, and not the OnLoad method, has further benefits in that it eliminates potential problems with sub-classes implementing Page_Load.

How The Process Works

The LoadViewState method, which is part of the Page’s initialisation phase, is only invoked during PostBack and therefore SaveViewState is the only method, of the two ViewState related methods, to be called when the page is first requested.

protected override object SaveViewState()
{
	Session["__ISREFRESH"] = _refreshState;
	object[] allStates = new object[2];
	allStates[0] = base.SaveViewState();
	allStates[1] = !_refreshState;
	return allStates;
}

Note: _refreshState (which on initial page request is defaulted to false and on subsequent PostBack requests is the value of ViewState) is assigned to the Session["__ISREFRESH"] item and the negated _refreshState is saved to the new ViewState.

Once a PostBack event takes place the LoadViewState method is called.

protected override void LoadViewState(object savedState)
{
	object[] allStates = (object[]) savedState;
	base.LoadViewState(allStates[0]);
	_refreshState = (bool) allStates[1];
	_isRefresh = _refreshState == (bool) Session["__ISREFRESH"];
}

Note: The _refreshState is retrieved from ViewState and compared with the value in the Session["__ISREFRESH"] item. The result is stored in _isRefresh, which is used by the IsRefresh Property.

The listing below shows the entire class definition:

namespace StevenBey.Web.UI
{
	public class Page : System.Web.UI.Page
	{
		private bool _refreshState;
		private bool _isRefresh;

		public bool IsRefresh
		{
			get
			{
				return _isRefresh;
			}
		}

		protected override void LoadViewState(object savedState)
		{
			object[] allStates = (object[]) savedState;
			base.LoadViewState(allStates[0]);
			_refrehState = (bool) allStates[1];
			_isRefresh = _refreshState == (bool) Session["__ISREFRESH"];
		}

		protected override object SaveViewState()
		{
			Session["__ISREFRESH"] = _refreshState;
			object[] allStates = new object[2];
			allStates[0] = base.SaveViewState();
			allStates[1] = !_refreshState;
			return allStates;
		}
	}
}

Testing The Process

<%@ Page Inherits="StevenBey.Web.UI.Page" %>
<html>
	<head>
		<title>Detecting Page Refresh</title>
	</head>
	<body>
		<form runat="server">
			<asp:button Text="Test Refresh" runat="server" />
		</form>
		IsRefresh = <%= IsRefresh %>
	</body>
</html>

Clicking the “Test Refresh” button invokes a PostBack, however the value of IsRefresh doesn’t change until you click on the browser’s Refresh button or press F5 on the keyboard (and then click “Retry”). Clicking the “Test Refresh” button once again resets the value of IsRefresh to false.

Live Demo

Conclusion

In this article I have demonstrated a simplified method of detecting a page refresh event.

Download the files used in this this article.

사용자가 새로고침 했을 경우를 나타내는 소스입니다.

영문으로 되어있으만 짧아서 보시는데 문제는 없을것 같군요.




소스: http://stevenbey.co.uk/detectingPageRefresh.aspx



데모: http://stevenbey.co.uk/detectingPageRefresh.demo.aspx

출처 : 태요

'.net' 카테고리의 다른 글

ConnectionStrings (1)	2007.10.08
SQLHelper.cs (1)	2007.10.05
web.config 암호화 (2)	2007.10.05
문자열의 선언 (0)	2007.09.27
ASP.NET AJAX를 지원하지 않는 웹호스팅에 AJAX 사용하기 (2)	2007.07.30

L2J with DuraBoys