Server-side controls need to be used judiciously, with server-side control
events being used only for click-events on buttons that would have been
SUBMIT buttons in classic CGI solutions. Having events fire on selections
from a drop-down list, for example, is probably not something would choose
to do other than in exceptional cases. The pitch for ASP.NET should be
supported by a great many advantages that it offers, the least of which is
server-side control events.
Steve Miller <[EMAIL PROTECTED]>
Sent by: The DOTNET list will be retired 7/1/02
<[EMAIL PROTECTED]>
06/26/2002 10:40 AM
Please respond to The DOTNET list will be retired 7/1/02
To: [EMAIL PROTECTED]
cc:
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.
_________________________________________________________________
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the material
from any computer.
You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
