I know that Response.Buffer has been replaced with Response.BufferOutput, but they should work regardless of which you use. I have used the .Buffer = False in the login page of my application and it seems to make the page take forever to load. As soon as I
turn on buffering the page loads the way it should. Now I can accept that this is just the way buffering works in ASP.NET, *BUT* the behavior is inconsistent on different platforms. I have not tried all combinations, but here is what I have discovered. 1.
XP server, XP Browser. ( dot NET 1.1, IE 6.0) a. Buffering turned off AND remote browser= Sloow page start, afterwards it is fast moving around in the app.. but if you kill the session (logout) and then attempt to re-create it (login) it is sloooow again.
b. Buffering turned off AND local browser = fast starts every time. c. Buffering turned on = Fast every time. 2. 2000 pro, 2000 Browser. ( dot NET 1.1, IE 6.0) a. Buffering turned off AND remote browser = fast starts all the time. b. Buffering turned on =
fast starts every time. I would like to try 2000 pro and an XP browser when I have the time. Does anyone have any ideas about why the inconsistent behavior under different systems, but the same browser version?... the XP version browser does have a bunch of
extra numbers "xpsp2.xxxxxxx" on the end of it, but everything before is the same as the 2000 browser version.
GH_Retro
Participant
982 Points
197 Posts
Response.Buffer functionality from asp -> asp.net
Jan 26, 2004 10:55 PM|LINK