Server Events vs. DHTML -- asp.net

asp.net : Server Events vs. DHTML

Steve C. Orr [MVP, MCSD]
4/2/2004 8:33:33 AM

Your understanding is correct.
If you don't need to post back to the server to handle something, then you
probably shouldn't. Client side code is a great way to keep your code
responsive and efficient.
If all your users are using a recent version of IE then this can work out
great for you, but if you have to support other browsers then it can be a
real pain to make sure your client side code works properly with all
browsers - you'd need to do a lot of testing and tweaking.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net

[quoted text, click to view]

Kevin Spencer
4/2/2004 11:09:20 AM

Sometimes one is more appropriate than the other. There are quite a few
considerations that make the determination. These include the type of
processing that needs to occur (some processing can only bo done on the
server), performance issues (you have brought up some of them), speed of
development, and code maintainablility, to name the most common.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

[quoted text, click to view]

Antonio Ooi
4/2/2004 10:15:18 PM

Hi,

I'm an application developer from Malaysia. I wanted to know how ASP.NET
server-side events vs. client-side DHTML for FORM manipulations, may be in
terms of performance and practicality? To my understanding, server events
will only work when user sends request to server. Any FORM object
manipulations will need to go through the Web server, whereas for DHTML, the
FORM objects are manipulated on the fly. The most beutiful thing of DHTML
is, clicking the 'Back' button will not go back to the previous user action
for the form but it dismisses the entire page. Need your advice on that.
Thanks in advance.

Best Regards,
Antonio

Antonio Ooi
4/3/2004 5:17:29 PM

Thanks for the ideas. I think as long as I can do the same for server-side
events of ASP.NET, whereby I can have a "< Back" button to go back to the
previous form and have all my previously entered values filled up, with the
minimum amount of codes, I will consider shifting my projects to ASP.NET. In
the conventional way, I need to issue only one line of code to have all my
previously entered values filled up, that is onclick="history.back()" in the
INPUT tag. Any workaround in ASP.NET in achieving the same result?

Thanks again!

Antonio
MCSD

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about asp.net

View Other Months
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008

home · blog · groups

Questions? Comments? Contact the dn