Sundar

Postbacks aren't necessarily a draw-back: you don't have to use them,
in that you can post to another page just as you used to in classic ASP.
In fact, sometimes, it's better to do it the old way.

You can still use your own javascript to handle client-side events and to be
honest,
if your projects need to be Netscape 4-and-above compliant, I would not rely
too much
on .NET's use of javascript.

Postbacks are useful for a number of reasons which are too many to go into
but in short, for example, <form runat="SERVER"> (with no attrtibutes added)
will cause the ASP.NET page to automatically postback to itself. Most of the
time,
this is good for performance because the page is already loaded.

The performance for ASP.NET and XSLT is pretty good and it's much easier to
work with
XML generally because of how tightly it's integrated with ADO.NET datasets,
not to mention
all the functionality in the System.Xml namespace.

Phil

-----Original Message-----
From: sundar srinivasan [mailto:ssrinivasan3@n...]
Sent: 05 August 2002 15:36
To: ASPX_Professional
Subject: [aspx_professional] asp .net & performance


I am currently using ASP, XML, XSLT. We have a framework that does a whole 
lot of client-side processing like multiple search, sort etc.
If I switch to ASP .net, would I get more programmer productivity by using 
web forms?

If any one has used xslt/xml and also ASP .Net, how would you rate the
performance? I have been hearing about .net's post-backs as a major 
drawback. Is that really so, meaning, does it post back everytime there's 
a handled event?