Question on viewstate workaround technique

[vMike]

I have a Datalist which contains linkbuttons. In order to get the
information about the clicked linkbutton I have been enabling the viewstate.
I have noticed that the size of the viewstate for datalists is quite large
(about 8000 character) even though the datalist ranges about 20 items long.
As a workaround I have thought about but haven't actually tried is to
disable the viewstate, then use the Request.Form("__EVENTARGET") and use the
control ID to determine which control has been click and process from there.
I also forgo getting any command arguments etc. The trade off here is page
bloat. What do you think of that method? Are there other ways to do this?
Thanks for any insight.

Mike

 

[Guest]

why can't you switch off the viewstate, and put a bit of ye olde client
script on the control in question, this can still call back to the server
side page?

i've had to use something like this to detect when someone presses 'enter'

 

[vMike]

why can't you switch off the viewstate, and put a bit of ye olde client
script on the control in question, this can still call back to the server
side page?

i've had to use something like this to detect when someone presses 'enter'

Thanks. Sometimes the simple things escape me.

 

[Guest]

I was in the middle of reading this when you posted
http://www.ondotnet.com/pub/a/dotnet/2003/09/15/aspnet.html

It has a couple of good ideas about asp.net & client script