ADBRITE ads links
You are here: CodeIdol > Ajax > Ajax with ASP.NET > page: 26 27 28 29 30 31 32 33 34 35 36
Developers no longer need to worry about processing state. With ASP.NET, actions are per-
formed within a series of events that provide statemachine-like functionality.
With the use of code-behind/beside model, code is separated from display. By separating code
and display files, there is less of a chance of designer and developer tools interfering with each
other.
A single development tool may be used for building the application and business logic. Having
a single integrated development suite allows developers to more easily interact with the appli-
cation logic. This results in more code reuse and fewer errors.
With the Visual Studio .NET IDE, ASP.NET supports many methods to debug and track a run-
ning ASP.NET.
Because ASP.NET is based on the common language runtime (CLR) and .NET, ASP.NET does
not suffer from the problems of COM. The .NET framework allows for multiple versions of
components to be on a system without interacting with each other.
ASP.NET is compiled. The first time that a file is loaded, it is compiled and then processed. The
compiled file is then saved into a temporary directory. Subsequent calls to the ASP.NET file are
processed from the compiled file. The execution of the compiled file on requests is faster than
the interpreted environment of Classic ASP.
All in all, ASP.NET is a dramatic improvement over ASP. It has become widely accepted in the develop-
ment community.
So, What's the Problem?
Based on what you have just read regarding ASP.NET, it may sound really good to you. You may be ask-
ing yourself, "Why is there a need for something else? What's the problem?"
The truth is ASP.NET has several issues that need to be addressed:
Round trips
-- The server events in ASP.NET require round trips to the server to process these
events. These round trips result in all form elements being sent between client and server as
well as images and other data files being sent back to the client from the server. While some web
browsers will cache images, there can still be significant data transfer.
Speed/network data transfer
-- Because of the
VIEWSTATE
hidden form element, the amount of
data that is transferred during a postback is relatively large. The more data and controls on the
page, the larger the
VIEWSTATE
will be and the more data that must be processed on the server
and transmitted back to the client.
Waiting on the result
-- When a user clicks on a button or some other visual element that posts
data back to the server, the user must wait on a full round trip to complete. This takes time
when the processing is done on the server and all of the data, including images and viewstate,
are returned to the client. During that time, even if the user attempts to do something with the
user interface, that action is not actually processed on the client.
4
Chapter 1
You are here: CodeIdol > Ajax > Ajax with ASP.NET > page: 26 27 28 29 30 31 32 33 34 35 36
|
|
Related tags
Popular Categories
Unix books and guides
AJAX popular information
C# language guides
Windows books and cookbooks
.......
|
|
