Ajax with ASP.NET

pdf.css

ADBRITE ads links

You are here: CodeIdol > Ajax > Ajax with ASP.NET > page: 26 27 28 29 30 31 32 33 34 35 36

Prevalence of spaghetti code
-- ASP code does not provide a structured development environ-
ment, often contributing to the creation of twisted and tangled "spaghetti code." ASP code is
literally a file with some basic configuration information at the top of every page. Each page
is executed from the top of the page to the bottom of the page. While it is possible to use
Component Object Model (COM) objects to eliminate some of the spaghetti code, this intro-
duces more complexity in the form of another development tool.

Lack of code separation
-- The code tends to be intermixed with display code. Intermixing the
code and the display logic requires that the tools that developers and designers use work well
together. This was often not the case. For example, it was well known that various visual devel-
opment tools could take a properly running ASP page, rearrange some of the code, and render
the ASP page broken.

Lack of code reusability
-- There is very little ability to reuse code within the ASP environment.

Lack of debugging support
-- Debugging an ASP application typically involves the use of
Response.Write
. This is in sharp contrast to an integrated development environment (IDE)
developed within a GUI environment.

Problems of COM
-- ASP is based on the Component Object Model and suffers from many of
the problems associated with COM. There were two major problems with COM.

The first was that updating COM objects tended to overwrite one object with the new
one. This could be problematic if a programming method call changed or any other new
behavior was introduced.

The second major problem with COM was that it was a binary standard. This binary
standard was based on a 32-bit programming model. As a result, COM objects would
not scale up to run natively within an environment that was an Intel-based 32-bit envi-
ronment. While this might not have been a big deal in the early to middle 1990s when
COM was designed and built, by the early 2000s and the introduction of inexpensive
64-bit systems, this was seen as a possible bottleneck.

Problems with being interpreted
-- ASP is interpreted. Each time an ASP file is loaded, the ASP
environment parses the ASP file, compiles the code, and then executes the file. This process is
repeated on each call to an ASP file. The result is wasted processing on the server.

Presence of the statemachine
-- ASP applications typically have a statemachine (in software
code, a statemachine is a section of code that depends on both its direct inputs and inputs made
during previous calls) at the top of every ASP page that processes the state of the user and then
displays code. Given that most client-side applications are built based on events, which is a sim-
ilar concept to a statemachine, this is an unfamiliar way to develop for developers not well
versed in ASP.
3
Introduction to Ajax on ASP.NET
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
.......