Misplaced Pages

Web application: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 11:56, 16 February 2022 view source116.72.171.225 (talk) unsourced information removed; please provide reliable sourcesTag: Reverted← Previous edit Revision as of 11:59, 16 February 2022 view source 116.72.171.225 (talk) unsourced information removed; please provide reliable sourcesTag: RevertedNext edit →
Line 1: Line 1:
{{short description|Application that uses a web browser as a client}} {{short description|Application that uses a web browser as a client}}
{{More citations needed|date=February 2018}} {{More citations needed|date=February 2018}}
{{Original research}}
] ]
A '''web application''' (or '''web app''') is application software that runs on a web server, unlike computer-based software programs that are run locally on the operating system (OS) of the device. Web applications are accessed by the user through a web browser with an active network connection. These applications are programmed using a client–server modeled structure—the user ("''client''") is provided ''services'' through an ''off-site server'' that is hosted by a third-party. Examples of commonly-used web applications include: web-mail, online retail sales, online banking, and online auctions. A '''web application''' (or '''web app''') is application software that runs on a web server, unlike computer-based software programs that are run locally on the operating system (OS) of the device. Web applications are accessed by the user through a web browser with an active network connection. These applications are programmed using a client–server modeled structure—the user ("''client''") is provided ''services'' through an ''off-site server'' that is hosted by a third-party. Examples of commonly-used web applications include: web-mail, online retail sales, online banking, and online auctions.

==Definition and similar terms==
{{More citations needed section|date=February 2018}}The general distinction between a ] of any kind and a "web app" is unclear. Web sites most likely to be referred to as "web applications" are those which have similar functionality to a desktop software application, or to a ]. ] introduced explicit language support for making applications that are loaded as web pages, but can store data locally and continue to function while offline.

]s are more application-like because they reject the more typical web paradigm of moving between distinct pages with different ]s. This is due to individual components being able to be replaced or updated without having to refresh the whole web page. Single-page frameworks might be used for speed development of such a web app for a mobile platform as it is able to save bandwidth, as well as the extinction of loading external files.

=== Mobile web application ===

{{further|Multiple phone web-based application framework}}

There are several ways of targeting mobile devices when making web applications:

* ] can be used to make a web application - whether a conventional website or a single-page application viewable on small screens that work well with touchscreens.
* ]s (PWAs) are web applications that load like regular web pages or websites but can offer the user functionality such as working offline and device hardware access traditionally available only to native mobile applications.
* Hybrid apps embed a web site inside a native app, possibly using a hybrid framework. This allows development using web technologies (and possibly directly copying code from an existing mobile web site) while also retaining certain advantages of native apps (e.g. direct access to device hardware, offline operation, app store visibility). Hybrid app frameworks include ], ], ], ], ] and ].


==History== ==History==


In 1995, ] introduced a ] language called ] allowing programmers to add some ] to the user interface that ran on the client side. So instead of sending data to the server in order to generate an entire web page, the embedded scripts of the downloaded page can perform various tasks such as input validation or showing/hiding parts of the page.<ref>{{Cite web|url=https://www.zdnet.com/article/javascript-creator-eich-my-take-on-20-years-of-the-worlds-top-programming-language/|title=JavaScript creator Eich: My take on 20 years of the world's top programming language|last=Liam Tung|website=]|date=2020-06-15}}</ref> In 1995, ] introduced a ] language called ] allowing programmers to add some ] to the user interface that ran on the client side. So instead of sending data to the server in order to generate an entire web page, the embedded scripts of the downloaded page can perform various tasks such as input validation or showing/hiding parts of the page.<ref>{{Cite web|url=https://www.zdnet.com/article/javascript-creator-eich-my-take-on-20-years-of-the-worlds-top-programming-language/|title=JavaScript creator Eich: My take on 20 years of the world's top programming language|last=Liam Tung|website=]|date=2020-06-15}}</ref>

In 1996, ] introduced ], a ] player that could be added to browsers as a ] 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. .<ref>{{Cite book |last1=Davidson |first1=James Duncan |url=http://java.sun.com/products/servlet/download.html |title=Java Servlet Specification ("Specification") Version: 2.2 Final Release |last2=Coward |first2=Danny |date=1999-12-17 |publisher=] |pages=43–46 |access-date=2008-07-27}}</ref> At that time both JavaScript and ] had already been developed, but ] had still not yet been coined and the ] object had only been recently introduced on Internet Explorer 5 as an ] object. In 1999, the "web application" concept was introduced in the Java language in the Servlet Specification version 2.2. .<ref>{{Cite book |last1=Davidson |first1=James Duncan |url=http://java.sun.com/products/servlet/download.html |title=Java Servlet Specification ("Specification") Version: 2.2 Final Release |last2=Coward |first2=Danny |date=1999-12-17 |publisher=] |pages=43–46 |access-date=2008-07-27}}</ref> At that time both JavaScript and ] had already been developed, but ] had still not yet been coined and the ] object had only been recently introduced on Internet Explorer 5 as an ] object.
Line 46: Line 30:


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 on the framework while another focuses on a specified use case. In applications which are exposed to constant ] attempts on the Internet, ] problems can be caused by errors in the program. ] can also promote the use of best practices<ref>{{cite web | url=http://docforge.com/Framework | title=Framework | author=Multiple (wiki) | work=Docforge | access-date=2010-03-06 }}{{dl|date=May 2021}}</ref> such as ]. 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 on the framework while another focuses on a specified use case. In applications which are exposed to constant ] attempts on the Internet, ] problems can be caused by errors in the program. ] can also promote the use of best practices<ref>{{cite web | url=http://docforge.com/Framework | title=Framework | author=Multiple (wiki) | work=Docforge | access-date=2010-03-06 }}{{dl|date=May 2021}}</ref> such as ].

In addition, there is potential for the development of applications on ]s, although currently there are not many viable platforms that fit this model.


==See also== ==See also==
Line 67: Line 49:


==References== ==References==
{{reflist}} {{reflist|2}}


==External links== ==External links==

Revision as of 11:59, 16 February 2022

Application that uses a web browser as a client
This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Web application" – news · newspapers · books · scholar · JSTOR (February 2018) (Learn how and when to remove this message)
This article possibly contains original research. Please improve it by verifying the claims made and adding inline citations. Statements consisting only of original research should be removed. (Learn how and when to remove this message)
Horde groupware is an open-source web application.

A web application (or web app) is application software that runs on a web server, unlike computer-based software programs that are run locally on the operating system (OS) of the device. Web applications are accessed by the user through a web browser with an active network connection. These applications are programmed using a client–server modeled structure—the user ("client") is provided services through an off-site server that is hosted by a third-party. Examples of commonly-used web applications include: web-mail, online retail sales, online banking, and online auctions.

History

In 1995, Netscape introduced a client-side scripting language called JavaScript allowing programmers to add some dynamic elements to the user interface that ran on the client side. So instead of sending data to the server in order to generate an entire web page, the embedded scripts of the downloaded page can perform various tasks such as input validation or showing/hiding parts of the page.

In 1999, the "web application" concept was introduced in the Java language in the Servlet Specification version 2.2. . At that time both JavaScript and XML had already been developed, but Ajax had still not yet been coined and the XMLHttpRequest object had only been recently introduced on Internet Explorer 5 as an ActiveX object.

In 2005, the term Ajax was coined, and applications like Gmail started to make their client sides more and more interactive. A web page script is able to contact the server for storing/retrieving data without downloading an entire web page.

Structure

Applications are usually broken into logical chunks called "tiers", where every tier is assigned a role. Traditional applications consist only of 1 tier, which resides on the client machine, but web applications lend themselves to an n-tiered approach by nature. Though many variations are possible, the most common structure is the three-tiered application. 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, CGI, ColdFusion, Dart, JSP/Java, Node.js, PHP, Python or Ruby on Rails) is the middle tier (application logic), and a database is the third tier (storage). 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 it may be beneficial to use an n-tiered approach, where the greatest benefit is breaking the business logic, which resides on the application tier, into a more fine-grained model. Another benefit may be 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. For example, the client data would be accessed by calling a "list_clients()" function instead of making an SQL query directly against the client table on the database. This allows the underlying database to be replaced without making any change to the other tiers.

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. 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. 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.

Business use

This section needs additional citations for verification. Please help improve this article by adding citations to reliable sources in this section. Unsourced material may be challenged and removed. (February 2018) (Learn how and when to remove this message)

Security breaches on these kinds of applications are a major concern because it can involve both enterprise information and private customer data. Protecting these assets is an important part of any web application and there are some key operational areas that must be included in the development process. This includes processes for authentication, authorization, asset handling, input, and logging and auditing. Building security into the applications from the beginning can be more effective and less disruptive in the long run.

Development

Writing web applications is often simplified by the use of web application framework. These frameworks facilitate rapid application development by allowing a development team to focus on the parts of their application which are unique to their goals without having to resolve common development issues such as user management. Many of the frameworks in use are open-source software.

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 on the framework while another focuses on a specified use case. In applications which are exposed to constant hacking attempts on the Internet, security-related problems can be caused by errors in the program. Frameworks can also promote the use of best practices such as GET after POST.

See also

References

  1. Liam Tung (2020-06-15). "JavaScript creator Eich: My take on 20 years of the world's top programming language". ZDNet.
  2. Davidson, James Duncan; Coward, Danny (1999-12-17). Java Servlet Specification ("Specification") Version: 2.2 Final Release. Sun Microsystems. pp. 43–46. Retrieved 2008-07-27.
  3. Jay Hoffmann (2019-03-04). "What Does AJAX Even Stand For?". Retrieved 2021-10-18.
  4. ^ Petersen, Jeremy (4 September 2008). "Benefits of using the n-tiered approach for web applications".
  5. "Top Tips for Secure App Development". Dell.com. Archived from the original on 2012-05-22. Retrieved 2012-06-22.
  6. Multiple (wiki). "Web application framework". Docforge. Retrieved 2010-03-06.
  7. Multiple (wiki). "Framework". Docforge. Retrieved 2010-03-06.

External links

Web interfaces
Server-side
Protocols
Server APIs
Apache modules
Topics
Client-side
Browser APIs
Web APIs
WHATWG
W3C
Khronos
Others
Topics
Related topics
Categories: