I argue that there is no more server side roundtrips then any other Web application. People that say this have not played around much with ASP.NET.
A common misconception The Server Side events happen when they happen on the client. This is not the case, yes many controls have an option to cause a postback. For instance dropdowns can cause a postback. The key is they can but don't have to. I have been to many a site that presents a dropdown of choices and once chosen another dropdown is filled with a postback and once one is chosen another dropdown is filled with a postback. These sites are developed with any number of development platforms. ASP.NET just makes this mucho easier. But a developer can turn off the auto-postback and still get a SelectedItemChanged event when the page is eventually posted back. A developer can get a Changed event for a TextBox when the page is eventually posted back. -----Original Message----- From: Steve Miller [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 26, 2002 9:40 AM To: [EMAIL PROTECTED] Subject: [DOTNET] Server side controls vs client side script. Some client-side code purist argue that ASP.NET's server side controls put to much of a load on the server and cause to many round trips to the server. When you are pitching ASP.NET and run into these arguments how do you answer these criticisms of ASP.NET? Steve Miller You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
