|
Written by Administrator
|
|
Tuesday, 06 May 2008 11:11 |
|
Cleveland Day of .NET is a free one day conference located at the Hilton Cleveland East/Beachwood hotel, targeted at developers using the Microsoft .NET platform. It is a collaborative effort among the various local user groups and is open to all developers, local or otherwise. This event is occurring on Saturday, May 17, 2008 from 8:00 AM to 5:30 PM. Cleveland has a lot of passionate, knowledgeable developers that have been asking for the opportunity to get together and share their knowledge with each other. Now we all have that chance! |
|
Read more...
|
|
|
State Management on ASP.NET - Part 2 |
|
|
|
|
Written by Administrator
|
|
Monday, 05 May 2008 14:05 |
|
Control State: Control State is new mechanism in ASP.NET 2.0 which addresses some of the shortcomings of View State. Control state can be used to store critical, private information across post backs. Control state is another type of state container reserved for controls to maintain their core behavioral functionality whereas View State only contains state to maintain control's contents (UI). Control State shares same memory data structures with View State. Control State can be propagated even though the View State for the control is disabled. For example, new control Grid View in ASP.NET 2.0 makes effective use of control state to maintain the state needed for its core behavior across post backs. Grid View is in no way affected when we disable View State for the Grid View or entire page Server Side State management: As name implies, state information will be maintained on the server. Application, Session, Cache and Database are different mechanisms for storing state on the server. Care must be taken to conserve server resources. For a high traffic web site with large number of concurrent users, usage of sessions object for state management can create load on server causing performance degradation |
|
Read more...
|
|
State Management on ASP.NET - Part 1 |
|
|
|
|
Written by Administrator
|
|
Monday, 05 May 2008 14:00 |
|
This article discusses various options for state management for web applications developed using ASP.NET. Generally, web applications are based on stateless HTTP protocol which does not retain any information about user requests. In typical client and server communication using HTTP protocol, page is created each time the page is requested.
Developer is forced to implement various state management techniques when developing applications which provide customized content and which "remembers" the user. Here we are here with various options for ASP.NET developer to implement state management techniques in their applications. Broadly, we can classify state management techniques as client side state management or server side state management. Each technique has its own pros and cons. Let's start with exploring client side state management options. |
|
Last Updated ( Tuesday, 06 May 2008 08:32 )
|
|
Read more...
|
|
|
|
|
|