Why Redraw of the whole page when paginating?

Hi, please look at the ASP.NET 2 site
http://www.prismatest.ch/catalog/EM.ASPX
(user=prismashop, password=minicooper). Use the ">" Button to go to the
next pages.
You will notice that the page goes all white every time after pressing
the ">" Button, and redraws itself only after all parts of the page
have been downloaded. This means the page stays white for several
seconds.
On most other sites, the current page stays on screen until the very
last moment, that means it never becomes all white. Altough the page
itself does not load faster than usual, the user experience is much
better, since he can always see "something". When the page goes all
white, the result is somewhat "flickering" and indicates a "slowness".
For example, take a look at this site:
http://www.citydisc.ch/s/search.cfm...&group_detail=0
Altough the site is quite slow, the page stays on-screen until the very
last moment when paginating, giving the user a better experience.
Does anyone know why this is happing? Is there a certain HTML or css
tag which causes this behaviour? I used lots of DIVs and SPANs and
stayed away from TABLEs where not appropriate (except for the title
bar). I also use lots of CSS. Is this the price I have to pay for
building a page with a "modern" apprach?
Thanks for any insight
UrsThere is a (poor working) option to do a similar thing in asp.net
However, i'm curious why 'these' websites refresh differently.
I see a total refresh on ordinary sites as well, so'
<urs@.prismanet.ch> schreef in bericht
news:1134120586.432050.120310@.g14g2000cwa.googlegroups.com...
> Hi, please look at the ASP.NET 2 site
> http://www.prismatest.ch/catalog/EM.ASPX
> (user=prismashop, password=minicooper). Use the ">" Button to go to the
> next pages.
> You will notice that the page goes all white every time after pressing
> the ">" Button, and redraws itself only after all parts of the page
> have been downloaded. This means the page stays white for several
> seconds.
> On most other sites, the current page stays on screen until the very
> last moment, that means it never becomes all white. Altough the page
> itself does not load faster than usual, the user experience is much
> better, since he can always see "something". When the page goes all
> white, the result is somewhat "flickering" and indicates a "slowness".
> For example, take a look at this site:
> http://www.citydisc.ch/s/search.cfm...&group_detail=0
> Altough the site is quite slow, the page stays on-screen until the very
> last moment when paginating, giving the user a better experience.
> Does anyone know why this is happing? Is there a certain HTML or css
> tag which causes this behaviour? I used lots of DIVs and SPANs and
> stayed away from TABLEs where not appropriate (except for the title
> bar). I also use lots of CSS. Is this the price I have to pay for
> building a page with a "modern" apprach?
> Thanks for any insight
> Urs
>
yes, the pages refresh totally on other sites, but there, not the whole
browser screen remains white for several seconds.
My first thought would be that it depends on the buffering option used
server side...
Patrice
<urs@.prismanet.ch> a crit dans le message de
news:1134136285.784010.321940@.f14g2000cwb.googlegroups.com...
> yes, the pages refresh totally on other sites, but there, not the whole
> browser screen remains white for several seconds.
>
buffering option? which buffe? where would I change that?
Ok likely not that then as this is likely on by default ?
Else see either the IIS configuration (this is in the options tab for the
IIS application configuration) or if you have something like
Response.Buffer=False in your code.
Bascially it either accumulates all the response in a buffer allowing to
send this in one shot when the page is ready.
Else this is sent in several chunk and the browser may not at first have
enough info to display something else than a blank page.
Not sure but could worth a try...
Patrice
<urs@.prismanet.ch> a crit dans le message de
news:1134142299.708187.32760@.f14g2000cwb.googlegroups.com...
> buffering option? which buffe? where would I change that?
>
Isn't this?:
Response.flush
<Do other heavy tasks like page.databind etc..>
Response.flush
"Patrice" <nobody@.nowhere.com> schreef in bericht
news:OUhLQaN$FHA.2308@.TK2MSFTNGP10.phx.gbl...
> Ok likely not that then as this is likely on by default ?
> Else see either the IIS configuration (this is in the options tab for the
> IIS application configuration) or if you have something like
> Response.Buffer=False in your code.
> Bascially it either accumulates all the response in a buffer allowing to
> send this in one shot when the page is ready.
> Else this is sent in several chunk and the browser may not at first have
> enough info to display something else than a blank page.
> Not sure but could worth a try...
> --
> Patrice
> <urs@.prismanet.ch> a crit dans le message de
> news:1134142299.708187.32760@.f14g2000cwb.googlegroups.com...
>
<pages buffer="true" /> in the system.web section of web.config should
flush the buffer
response.flush is more for long running processes where you want to
show some form of status, update
Not sure what that does yet.
I include a meta no-chache in allmost all my pages.
Hopefully yours will not overrule that ?
"CJ" <Charles.Deisler@.gmail.com> schreef in bericht
news:1134274947.508314.285740@.g44g2000cwa.googlegroups.com...
> <pages buffer="true" /> in the system.web section of web.config should
> flush the buffer
> response.flush is more for long running processes where you want to
> show some form of status, update
>
There's a great article here..
http://msdn.microsoft.com/library/d...
etchapt06.asp
regards-