Web application
From Wikipedia, the free encyclopedia
 |
This article or section includes a list of references or external links, but its sources remain unclear because it lacks inline citations. You can improve this article by introducing more precise citations where appropriate. (February 2008) |
 |
It has been suggested that Rich Internet application be merged into this article or section. (Discuss) |
 |
The neutrality of this article is disputed. Please see the discussion on the talk page. (July 2008) Please do not remove this message until the dispute is resolved. |
In software engineering, a web application or webapp [1] is an application that is accessed via web browser over a network such as the Internet or an intranet. It is also a computer software application that is coded in a browser-supported language (such as HTML, JavaScript, Java, etc.) and reliant on a common web browser to render the application executable.
Web applications are popular due to the ubiquity of a client, sometimes called a thin client. The ability to update and maintain web applications without distributing and installing software on potentially thousands of client computers is a key reason for their popularity. Common web applications include webmail, online retail sales, online auctions, wikis, massively multiplayer online role-playing games and many other functions.
Contents |
[edit] History
In earlier types of client-server computing, each application had its own client program which served as its user interface and had to be separately installed on each user's personal computer. An upgrade to the server part of the application would typically require an upgrade to the clients installed on each user workstation, adding to the support cost and decreasing productivity.
In contrast, web applications use web documents written in a standard format such as HTML (and more recently XHTML), which are supported by a variety of web browsers.
Generally, each individual web page is delivered to the client as a static document, but the sequence of pages can provide an interactive experience, as user input is returned through web form elements embedded in the page markup. During the session, the web browser interprets and displays the pages, and acts as the universal client for any web application.
In 1995, Netscape introduced a client-side scripting called JavaScript, which allowed programmers to add some dynamic elements to the user interface that ran on the client side. Until then, all the data had to be sent to the server for processing, and the results were delivered through static HTML pages sent back to the client.
In 1996, Macromedia introduced Flash, a vector animation player that could be added to browsers as a plugin to embed animations on the web pages. It allowed the use of a scripting language to program interactions on the client side with no need to communicate with the server.
In 1999, the "web application" concept was introduced in the Java language in the Servlet Specification version 2.2. [2.1?]. [1][2] At that time both JavaScript and XML had already been developed, but AJAX had not still been coined and the XMLHttpRequest object had only been recently introduced on Internet Explorer 5 as an ActiveX object. [3]
In 2004, Web 2.0 was coined, and it was proposed to use the Web as a platform, [4] as opposed to simply developing applications that used Internet to communicate with the server.
In 2005, AJAX was coined, and applications like Gmail started to make their client sides more and more interactive.
[edit] Interface
The web interface places very few limits on client functionality. Through Java, JavaScript, DHTML, Flash and other technologies, application-specific methods such as drawing on the screen, playing audio, and access to the keyboard and mouse are all possible. Many services have worked to combine all of these into a more familiar interface that adopts the appearance of an operating system. General purpose techniques such as drag and drop are also supported by these technologies. Web developers often use client-side scripting to add functionality, especially to create an interactive experience that does not require page reloading (which many users find disruptive)[citation needed]. Recently, technologies have been developed to coordinate client-side scripting with server-side technologies such as PHP. Ajax, a web development technique using a combination of various technologies, is an example of technology which creates a more interactive experience.
[edit] Technical considerations
A significant advantage of building web applications to support standard browser features is that they should perform as specified regardless of the operating system or OS version installed on a given client. Rather than creating clients for MS Windows, Mac OS X, Linux, and other operating systems, the application can be written once and deployed almost anywhere. However, inconsistent implementations of the HTML, CSS, DOM and other browser specifications can cause problems in web application development and support. Additionally, the ability of users to customize many of the display settings of their browser (such as selecting different font sizes, colors, and typefaces, or disabling scripting support) can interfere with consistent implementation of a web application.
Another approach is to use Adobe Flash or Java applets to provide some or all of the user interface. Since most web browsers include support for these technologies (usually through plug-ins), Flash- or Java-based applications can be implemented with much of the same ease of deployment. Because they allow the programmer greater control over the interface, they bypass many browser-configuration issues, although incompatibilities between Java or Flash implementations on the client can introduce different complications. Because of their architectural similarities to traditional client-server applications, with a somewhat "thick" client, there is some dispute over whether to call systems of this sort "web applications"; an alternative term is "Rich Internet Application" (RIA).
[edit] Structure
Applications are usually broken into logical chunks called "tiers", where every tier is assigned a role.[5] Traditional applications consist only of 1 tier, which resides on the client machine, but web applications lend themselves to a n-tiered approach by nature.[5] Though many variations are possible, the most common structure is the three-tiered application.[5] In its most common form, the three tiers are called presentation, application and storage, in this order. A web browser is the first tier (presentation), an engine using some dynamic Web content technology (such as ASP, ASP.NET, CGI, ColdFusion, JSP/Java, PHP, Perl, Python, or Ruby on Rails) is the middle tier (application logic), and a database is the third tier (storage).[5] The web browser sends requests to the middle tier, which services them by making queries and updates against the database and generates a user interface.
For more complex applications, a 3-tier solution may fall short, and you may need a n-tiered approach, where the greatest benefit is breaking the business logic, which resides on the application tier, into a more fine-grained model.[5] For example, creating a separate business logic tier. Or adding an integration tier that separates the data tier from the rest of tiers by providing an easy-to-use interface to access the data.[5] For example, you would access the client data by calling a "list_clients()" function instead of making a SQL query directly against the client table on the database. That allows to replace the underlying database without changing the other tiers.[5]
There are some who view a web application as a two-tier architecture. This can be a "smart" client that performs all the work and queries a "dumb" server, or a "dumb" client that relies on a "smart" server. [5] The client would handle the presentation tier, the server would have the database (storage tier), and the business logic (application tier) would be on one of them or on both. [5] While this increases the scalability of the applications and separates the display and the database, it still doesn't allow for true specialization of layers, so most applications will outgrow this model.[5]
[edit] Business use
An emerging strategy for application software companies is to provide web access to software previously distributed as local applications. Depending on the type of application, it may require the development of an entirely different browser-based interface, or merely adapting an existing application to use different presentation technology. These programs allow the user to pay a monthly or yearly fee for use of a software application without having to install it on a local hard drive. A company which follows this strategy is known as an application service provider (ASP), and ASPs are currently receiving much attention in the software industry.
[edit] Writing web applications
There are many web application frameworks which facilitate rapid application development by allowing the programmer to define a high-level description of the program. In addition, there is potential for the development of applications on Internet operating systems, although currently there are not many viable platforms that fit this model.
The use of web application frameworks can often reduce the number of errors in a program, both by making the code simpler, and by allowing one team to concentrate just on the framework. In applications which are exposed to constant hacking attempts on the Internet, security-related problems caused by errors in the program are a big issue. Frameworks may also promote the use of best practices such as GET after POST.
[edit] Web application security
The Web Application Security Consortium (WASC) and OWASP are projects developed with the intention of documenting how to avoid security problems in web applications. A web application security scanner is specialized software for detecting security problems in web applications.
[edit] Applications
Browser applications typically include simple office software (word processors, online spreadsheets, and presentation tools), with Google Docs being the most notable example, and can also include more advanced applications such as project management, computer-aided design, and point-of-sale
[edit] Benefits
Browser applications typically require little or no disk space on the client, upgrade automatically with new features, integrate easily into other web procedures, such as email and searching. They also provide cross-platform compatibility (i.e., Windows, Mac, Linux, etc.) because they operate within a web browser window.
[edit] Disadvantages
Standards compliance is an issue with any non-typical office document creator, which causes problems when file sharing and collaboration becomes critical. Also, browser applications rely on application files accessed on remote servers through the Internet. Therefore, when connection is interrupted, the application is no longer usable. Google Gears is a platform to ameliorate this issue and improve the usability of browser applications.
[edit] See also
[edit] References
- ^ a b Alex Chaffee (2000-08-17). "What is a web application (or "webapp")?". Retrieved on 2008-07-27.
- ^ James Duncan Davidson, Danny Coward (17-12-1999). Java™Servlet Specification ("Specification") Version: 2.2 Final Release, Sun Microsystems. pp. 43-46, http://java.sun.com/products/servlet/download.html. Retrieved on 27 July 2008.
- ^ "Dynamic HTML and XML: The XMLHttpRequest Object". Apple Inc. Retrieved on 2008-06-25.
- ^ Tim O'Reilly (2006-12-10). "Web 2.0 Compact Definition: Trying Again". Retrieved on 2007-01-20.
- ^ a b c d e f g h i j Jeremy Petersen. "Benefits of using the n-tiered approach for web applications".
[edit] External links
- HTML 5 Draft recommendation, changes to HTML and related APIs to ease authoring of web-based applications.
- The Other Road Ahead — An article arguing that the future lies on the server, not rich interfaces on the client
- Web Applications in the Open Directory Project
