Web User control and Marshelling b/w client browser and web server(database).

[Al]

hi, I am new to asp.net. I have a question about
Marshelling b/w client browser and web server(database). I
heared that it is better to minimize going back and forth
b/w client browser and the server.This will increase
performance and improve scallability.
With asp.net, using server controls. It seems every action
at the client browser require a trip to the server, for
instance, page_load ( to fill combo boxes), or the event
of the combo boxes to fill other dependant combo box. or
when using the server validation controls.
What I am trying to get into is that how come asp.net
development favour using web server controls
[runat="server] even when there is cost (lots of
marshelling b/w client browser and the server)
Or my thinking is wrong.
I would appreciate your feedback to make things clear to
me.
thanks
Al

 

[Alvin Bruney]

It's not an ASP.NET rule. It is just abused to the point where it is
accepted. Asp.Net doesn't require all controls to be webserver controls. In
fact there are two families of controls. These must be used with enough care
and attention so that the advantages are exploited and the disadvantages
minimized. Webserver controls are heavy, if all you need is a light weight
control, there is no need for a webserver control and Asp.Net doesn't
recommend against this approach, infact it is supported.

Regards,
Alvin Bruney
http://www.networkip.net/dotnet/tidbits/default.htm