RE: Bees knees of grid controls for ASP.NET

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Steven Cheng[MSFT] (v-schang_at_online.microsoft.com)
Date: 01/25/05 

Date: Tue, 25 Jan 2005 04:11:13 GMT

Hi Rob,

The too post-back intensive of the asp.net grid control is due to the
fundamental of the web application (such as asp.net, asp , jsp...). In web
page since the clientside use webbrowser to retrieve page from remote site
and display locally, there is no persistent connection between client and
server, all communication is stateless request/response based. So generally
it's hard to make stateful interactive UI like those in winform(desktop
app). However, asp.net provide a rich form/control based programming
framework which make the web page development much eaiser and structural,
but this is done by hidden the underlying stateless request/response, so
we'll see that most of the asp.net powerful controls such as datagrid,
calendar, need to do postback to maintain the status. Also, we can use much
more clientside scripts or browser supported behaviors to make the
clientside UI more powerful(and there does exists some 3rd party controls
providing such fucntions), but this'll make the application too dependent
on the clientside enviorment, and too "POWERFUL' client side behavior(
except those that use activex or hosted winform control) is consided not
very stable. So generally the compatibility will be the most important
point for web application.

If there're any further questions or ideas, please feel free to post here.
Thanks.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Quantcast