EVOLUTION OF WEB DEVELOPMENT

THE EVOLUTION OF WEB DEVELOPMENT

m.sarulatha
Assistant Professor,
Dept. of CA, JJC.

The Internet began in the late 1960's as a test. Its goal was to create a robust information network - which could tolerate the loss of many computers without preventing others from connecting. Driven by potential disaster situations (such as nuclear attacks), the U.S. Department of Defense has provided initial funding.

Early Internet was restricted to educational institutions and defense contractors. It has grown as a tool for academic collaboration, allowing researchers around the world to share information. In the early 1990's, modems were developed that could work beyond existing phones, and the Internet began to open up to commercial users. In 1993, the first HTML browser was developed, and the Internet revolution began.

HTML and HTML forms

It will be difficult to define original websites as web applications. Instead, the first generation of websites sometimes looked like brochures, with organized HTML pages that needed to be manually updated.

A basic HTML page is like a document that uses words — it contains content formatted that can be displayed on your computer, but it actually does nothing. The following example illustrates HTML simply, with text containing a title and one line of text:

<html>

<head>

<title>Sample Web Page</title>

</head>

<body>

<h1>Sample Web Page Heading</h1>

<p>This is a sample web page.</p>

</body>

</html>

An HTML document has two types of content: text and objects (or tags) that tell the browser how to format it. The elements are easily recognizable, as they are designed in brackets (<>).

HTML defines elements of different levels of headers, categories, links, italic and bold inserts, horizontal lines, and so on. For example, <h1> Other Text </h1> uses the <h1> object. This component tells the browser to display a specific Text in the style of title 1, using a large, bold font.

Similarly, <p> This is a sample web page. </p> creates a single line of text. The <head> element combines the header information together, including the title that appears in the browser window, while the <untu> groups include the actual content of the document displayed in the browser window.

Figure 1-1 shows this simple HTML page in the browser. Currently, this is just an edited file (provided sample_web_page_heading.htm) that contains HTML content. It has no interruptions, does not require a web server, and certainly cannot be considered a web application.

Figure 1.1. Standard HTML: site "brochure"

HTML 2.0 introduced the first seed of web programming with a technology called HTML forms. HTML forms expand HTML so that it includes not only formatting tags but also tags for graphical widgets, or controls. These controls include common ingredients such as drop-down lists, text boxes, and buttons. Here's a sample web page created with HTML form controls:

<html>

<head>

<title>Sample Web Page</title>

</head>

<body>

<form>

This is choice #1<br />

This is choice #2<br /><br />

</form>

</body>

</html>

In an HTML form, all controls are placed between the <form> and </form> tags. The preceding example includes two check boxes (represented by the <input type="checkbox" /> element) and a button (represented by the <input type="submit" /> element). The <br /> element adds a line break in between lines. In a browser, this page looks like Figure 1-2.

Figure 1.2. An HTML form

HTML forms allow web application developers to design custom input pages. When a user clicks the Move button on the page shown in Figure 1-2, all the details in the input settings (in this case, two checkboxes) are integrated into a single text string and sent to a web server. On the server side, the customization system detects and processes data.

Surprisingly, the controls built on HTML forms over the past decade are still the basic framework you will use to build dynamic ASP.NET pages! The difference is the type of application that works on the server side. In the past, when a user clicked a button on a form page, the information may have been emailed to a pre-set account or sent to an application on a server that used the Common Commonway Interface (CGI) challenge. Today, you will be working with the most efficient and excellent ASP.NET platform.

Server-Side Program

why ASP.NET was created, helps to understand the problems of early web development technologies. For the original CGI type, for example, the web server must present a completely different application model for each web application. If a website is popular, the web server struggles under the weight of hundreds of different copies of the application, eventually becoming a victim of its own success. In addition, technologies such as CGI provide an environment for empty systems. If you are looking for advanced features, such as the ability to authenticate users, keep personal information, or display records you have received from a database, you need to write code pages from scratch. Building a web system in this way is prone and flawed.

To address these issues, Microsoft has created state-of-the-art platforms, such as ASP and ASP.NET. Both of these technologies allow developers to dynamic web pages without having to worry about low usage details. As a result, both platforms are surprisingly successful.

The first ASP platform gained nearly a million viewers, much more popular than Microsoft expected. It was not long before it was divided into all sorts of unfamiliar areas, including critical business applications and highly commercially available e-commerce sites. Because the ASP is not built on these intellectual property, performance, safety, and suspension problems.

This is where ASP.NET comes into play. ASP.NET was developed as an industry application web application that can address ASP limitations. Compared to the older ASP, ASP.NET offers better performance, better design tools, and a richer set of ready-made logos. ASP.NET has been very popular since its release - in fact, it ran on many commercial beta-powered websites.

NOTE

Despite having the same understanding, ASP and ASP.NET are very different. ASP is a text-based editing language that requires a full understanding of HTML and good coding skills. ASP.NET, on the other hand, is an object-based programming model that allows you to integrate a web page as easily as you would a Windows program. The sidebar "The Many Faces of ASP.NET," which appears later in this chapter, explains more about the variety of ASP.NET.

Client-Side Program

At a time when web development on the server was going through a tech revolution, a new type of programming was gaining popularity. Developers have begun experimenting with various ways to optimize web pages by embedding small applets built with JavaScript, ActiveX, Java, and Flash into web pages. This client technology technology does not involve server configuration Instead, the full application is downloaded to the client browser, which we use locally.

The biggest problem with customer case technology is that they are not evenly supported by all the browsers and operating systems. One of the reasons why web development is so popular in the first place is because web applications do not require CDs to set up, download, and other critical steps (and errors).

Instead, the web system can be used on any computer with Internet access. But when developers use customer case technology, they encounter a common subtle headache. Suddenly, the compatibility of the rotating browser becomes a problem. Developers are forced to test their websites with different operating systems and browsers, and may also need to distribute browser updates to their customers. In other words, the client-side model offers the most important benefits of web development.

For that reason, ASP.NET is designed as a server-side technology. All ASP.NET code pulls out of the server. When the code is finished, the user gets a standard HTML page, which can be viewed in any browser. Figure 1 shows the difference between a server-side and a client-side model.

Here are some reasons to avoid the client-side system:

Isolation

Client sidebar cannot access server-side services. For example, the client-side application does not have an easy way to read the file or interact with the database on the server (at least not without getting into security issues with the browser compliance).

Security

End users can view the client's side code. And when malicious users understand how an app works, they tend to be distracted.

Thin clients

As the Internet continues to emerge, web-enabled devices such as phones, palm computers, and PDAs (digital assistants) are emerging. These devices can communicate with web servers, but they do not support all aspects of a traditional browser. Your major clients may use server-based web applications, but they will not support third-party features such as JavaScript.

However, third-party customer systems are dead. In most cases, ASP.NET allows it.

Figure 1.3. Server-side and client-side web applications

Search This Blog

Yaazh