By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,871 Members | 2,595 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,871 IT Pros & Developers. It's quick & easy.

.NET Web Forms (Postbacks) VS. Clent Side Java Script.

P: n/a
OK, have I come full circle.... ?

1) .NET with VS Studio seemed to be the answer to all my prayers.
A) No more worries about coding for Netscape vs. IE.
B) Quick Deployment
C) All code in code behind.
D) Go .NET

So I re-wrote the whole application in .NET code behind.

Then the penalty for all the post backs....

So I rewrote the 90% of the application back to Client Side Java Script.

VS.NET is a great tool (especially the debug) and I learned a great deal,
but other than the Datagrid, which I use only for the paging capability, I
am missing the benefit of .NET. For a web business application, XML HTTP
Posts to the web server and DHTML seems to be a much faster solution than
using the Postbacks in .NET.

The lack of persistence for controls generated at run time seem to pose a
great many challenges even if I could live with all the post backs. This
comment is really just a side note, I am more curious to get some feedback
on the comments above regarding Postbacks vs. Javascript and HTTP Posts.

I would appreciate any comments just in case I am missing some big picture.
I seem to be looking for a server side tool that is somehow client side
aware so that I can modify just pieces of the client side page without all
the postback overhead.

Thanks for any comments in advance.

Jim
Jul 21 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hello

Personally, I can't live without both javascript/dhtml and post back. I
always use a combination of both. It is up to you to choose the most
appropriate way for your solution needs, your target clients and
environment.

You can use WebControls that use javascript and dhtml on high level browsers
while still using post backs on low level browsers. Depending on your needs,
you can either develop your own controls or use one of many free or
commercial third party controls available.

If you are looking for examples, I think Internet Explorer Web Controls is a
very good example, source is available at
http://www.asp.net/IEWebControls/Dow...ndex=0&tabid=1

Best Regards
Sherif

"Jim Mitchell" <ji**********@mindspring.com> wrote in message
news:e6**************@TK2MSFTNGP09.phx.gbl...
OK, have I come full circle.... ?

1) .NET with VS Studio seemed to be the answer to all my prayers.
A) No more worries about coding for Netscape vs. IE.
B) Quick Deployment
C) All code in code behind.
D) Go .NET

So I re-wrote the whole application in .NET code behind.

Then the penalty for all the post backs....

So I rewrote the 90% of the application back to Client Side Java Script.

VS.NET is a great tool (especially the debug) and I learned a great deal,
but other than the Datagrid, which I use only for the paging capability, I
am missing the benefit of .NET. For a web business application, XML HTTP
Posts to the web server and DHTML seems to be a much faster solution than
using the Postbacks in .NET.

The lack of persistence for controls generated at run time seem to pose a
great many challenges even if I could live with all the post backs. This
comment is really just a side note, I am more curious to get some feedback
on the comments above regarding Postbacks vs. Javascript and HTTP Posts.

I would appreciate any comments just in case I am missing some big picture. I seem to be looking for a server side tool that is somehow client side
aware so that I can modify just pieces of the client side page without all
the postback overhead.

Thanks for any comments in advance.

Jim

Jul 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.