Large (over 1 meg) website takes long time to post back W/O Viewst

[William Sullivan]

I've got a website that may, on occasion, display a large list of items in a
bulletedlist control. On the client side, it takes about 4 seconds to get a
response that weighs in at over 1mb. It takes less than a second to display
those nodes. That part is fine

The problem is that when the user causes a postback, the browser appears to
lock up for anywhere between 10-20 seconds, at which point it renders the
response from the server.

Examining the communication with Fiddler, I can see that the browser is not
returning the list data in the postback (only 78k bytes are being returned to
the server), which makes sense because I've turned off the viewstate on that
control. I can also see that the request completes its round trip in under
three seconds, starting when the user causes the postback, even though the
browser is still locked up and won't respond for another twenty or so
seconds. This behavior happens in IE6, firefox 1.5whatever and navigator.

In addition to turning off the viewstate for the control, I have also turned
off viewstate encryption for the page, viewstate MAC and event validation.
None of these have helped.

Does anyone know what might be causing this to happen? Are there other
workarounds I can try to prevent this from happening? If I can't fix this
problem, I'm going to have to end up using data paging, which is going to be
a nightmare with my back end. No pun intended. TIA!

[bruce barker \(sqlwork.com\)]

you are probably hitting the rendering time. the browser is designed to
render one page, which it expects to be a readable page (10k-50k or so).
long tables or list will render slowly if they get much beyond 20 rows.

you need to implement some form of paging in the web world. 1 mb

-- bruce (sqlwork.com)

"William Sullivan" <Wi************ *@discussions.m icrosoft.comwro te in
message news:09******** *************** ***********@mic rosoft.com...

I've got a website that may, on occasion, display a large list of items in
a
bulletedlist control. On the client side, it takes about 4 seconds to get
a
response that weighs in at over 1mb. It takes less than a second to
display
those nodes. That part is fine

The problem is that when the user causes a postback, the browser appears
to
lock up for anywhere between 10-20 seconds, at which point it renders the
response from the server.

Examining the communication with Fiddler, I can see that the browser is
not
returning the list data in the postback (only 78k bytes are being returned
to
the server), which makes sense because I've turned off the viewstate on
that
control. I can also see that the request completes its round trip in
under
three seconds, starting when the user causes the postback, even though the
browser is still locked up and won't respond for another twenty or so
seconds. This behavior happens in IE6, firefox 1.5whatever and navigator.

In addition to turning off the viewstate for the control, I have also
turned
off viewstate encryption for the page, viewstate MAC and event validation.
None of these have helped.

Does anyone know what might be causing this to happen? Are there other
workarounds I can try to prevent this from happening? If I can't fix this
problem, I'm going to have to end up using data paging, which is going to
be
a nightmare with my back end. No pun intended. TIA!