[Mono-bugs] [Bug 48689][Min] Changed - Visible is not saved at SaveViewState
Mon, 29 Sep 2003 03:59:30 -0400 (EDT)
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by firstname.lastname@example.org.
--- shadow/48689 2003-09-29 03:37:20.000000000 -0400
+++ shadow/48689.tmp.32141 2003-09-29 03:59:30.000000000 -0400
@@ -50,6 +50,23 @@
using an int as a bit field. That way we can save Visible, Enabled and
others boolean values, while not making VS grow too much.
I think I'm gonna do that pretty soon. The other 'reduction' is using
hexadecimal numbers instead of decimal ones or even binary. I'll do
some testing... and then store Visible too.
+------- Additional Comments From email@example.com 2003-09-29 03:59 -------
+OK, at any case I think that we should save this one just to be on
+the safe side.
+About reducing the ViewState size I believe the true "bottle-neck" is
+our page mechanism. As far as I've seen there are more "calls" (round-
+trips) in our mechnism than the one of MS.
+Don't forget that changing into bit fields etc. is a big change.
+We work quite hard to stabilize the web controls and such change
+should be done carefully, step by step. (Not that I don't trust
+you... :-) ).
+I must say that by looking on the ViewState I didn't have the feeling
+that it's filled with a lot of data and let's not forget that the
+variables are "located" on the server only so I don't know if this is
+Maybe it will be good for compatibility issue.