[thelist] RE: storing data clientside

[Peter Brunone (EasyListBox.com)]

Tim,

	You're right; it does have its uses.  I guess I've just gotten
into the mindset of the control developer, where I choose what mechanism
to implement at the control level (whereas the native ASP.NET web
controls already have that decided for them).
	For my own purposes -- in building EasyListBox, that is --
Request.Form/Querystring/Cookies takes care of the selected values, and
checksum caching is a great way to keep the data around.

-----Original Message-----
From: thelist-bounces at lists.evolt.org On Behalf Of Tim Kuhn

Peter, 

You are absolutely correct that you cannot access Viewstate from the
client. I was just thinking of storing data on the client, not accessing
it from there. I wasn't thinking, too early in the morning I guess.
While I do agree that Viewstate can be a bad thing when used
inappropriately, and is commonly abused, it does have its uses.

------------------------------
Tim,

	Actually, you can't really access ViewState from the client side
at all; it's solely a method of maintaining data across web requests.

	As much as I make my living off ASP.NET, I really dislike
ViewState, since the same thing could be accomplished in a number of
less-annoying ways.  ASP.NET 2.0 should provide some much better
state-maintenance methods.

	What about just using a client-side array that stays in a hidden
frame or something?

Cheers,

Peter