Wrox Programmer Forums
Go Back   Wrox Programmer Forums > ASP.NET and ASP > Other ASP.NET > ASP.NET 1.x and 2.0 Application Design
ASP.NET 1.x and 2.0 Application Design Application design with ASP.NET 1.0, 1.1, and 2.0.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 1.x and 2.0 Application Design section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old August 18th, 2005, 04:14 PM
Registered User
Join Date: Feb 2005
Posts: 7
Thanks: 0
Thanked 0 Times in 0 Posts
Default Session State|View State|Do I have other options?


Is their a better way of addressing/passing datasets from one aspx page to another than using SessionState or ViewState. The problem with SessionState requires a trip back to the server and ViewState suffers performance issues when the dataset is too big?


Old August 19th, 2005, 12:08 AM
Friend of Wrox
Join Date: Nov 2003
Posts: 1,348
Thanks: 0
Thanked 5 Times in 5 Posts

You can use object cashing to cache the dataset.

Old October 5th, 2005, 07:10 PM
Registered User
Join Date: Oct 2005
Posts: 8
Thanks: 0
Thanked 0 Times in 0 Posts

I thought the object Cache could only be used for the application and not the session

I do have some questions though.

First: What is meant by a session variable requiring a round trip to the server? I thought that the only way of storing data on the users computer was with a cookie and it had to be retrieved by the application and then sent back to the server with the new page essentially making a round trip. Isn't the Session state variable stored on the server? If so why would it have to make a round trip? Doesn't the server just fill in the new page with the data before it sends it.

The second question is about the Cache object, What are the benefits of using this instead of an application variable. Both are destroyed when the application ends. The only differences I can tell are the providing of datalocks for the cache object (which would only be needed if your application is updating the data) and the fact that an application variable is created on startup while a cache object is not created until the first time it is used. The Cache object would thus have more overhead because of the locks and the Cache management.

If there is more to it than that then I need to know because it could be something I need to look at it for the application I'm working on now.

Similar Threads
Thread Thread Starter Forum Replies Last Post
View state problem rabbit3 ASP.NET 2.0 Professional 0 October 23rd, 2007 08:55 PM
Javascript and View State VictorVictor ASP.NET 2.0 Professional 8 April 2nd, 2007 02:34 PM
how to use view state in code behind files in C# ajeshss C# 4 June 20th, 2006 06:00 AM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.