K
Ken Varn
I am trying to cut down the amount ViewState data that is passed to the
client browser. I have a number of Web Server Controls on my page, but I am
confused as to when ViewState can be disabled to save on web traffic.
For instance.... I have several drop down listboxes. If I disable
ViewState, then my server side code cannot obtain the selected item when the
form is submitted. The thing that confuses me is that this should be
submitted back as part of the form regardless of the setting for ViewState,
so why is it necessary to enable ViewState to get the selected index? If I
disable ViewState, then the drop down list fails with an exception if I try
to access the SelectedItem.Value property.
The main point of confusion is that I don't have anyway of knowing what I
lose when I disable ViewState for any given control.
--
-----------------------------------
Ken Varn
Senior Software Engineer
Diebold Inc.
EmailID = varnk
Domain = Diebold.com
-----------------------------------
client browser. I have a number of Web Server Controls on my page, but I am
confused as to when ViewState can be disabled to save on web traffic.
For instance.... I have several drop down listboxes. If I disable
ViewState, then my server side code cannot obtain the selected item when the
form is submitted. The thing that confuses me is that this should be
submitted back as part of the form regardless of the setting for ViewState,
so why is it necessary to enable ViewState to get the selected index? If I
disable ViewState, then the drop down list fails with an exception if I try
to access the SelectedItem.Value property.
The main point of confusion is that I don't have anyway of knowing what I
lose when I disable ViewState for any given control.
--
-----------------------------------
Ken Varn
Senior Software Engineer
Diebold Inc.
EmailID = varnk
Domain = Diebold.com
-----------------------------------