| Revision as of 07:08, 30 September 2024 view sourceGraham87 (talk | contribs)Autopatrolled, Event coordinators, Extended confirmed users, Page movers, Importers291,544 editsm rv back to AprilTag: Manual revert← Previous edit | Revision as of 04:22, 23 October 2024 view source Nfarrow93 (talk | contribs)61 edits Restructured section to start with the introduction of web applications before covering the background. When discussing history, it feels more appropriate to provide the reader with the main subject being discussed first. Once they know what the section is about, then dive into the history of how the subject formed.Tag: Visual editNext edit → | ||
| Line 24: | Line 24: | ||
| ==History== | ==History== | ||
| The concept of a "web application" was first introduced in the Java language in the Servlet Specification version 2.2, which was released in 1999. At that time, both JavaScript and ] had already been developed, but the ] object had only been recently introduced on Internet Explorer 5 as an ] object.<sup>]'']</sup> Beginning around the early 2000s, applications such as "] (2003), ] (2004), ] (2004), ] (2005)," 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. The practice became known as Ajax in 2005. | |||
| ⚫ | In earlier computing models like client-server, the processing load for the application was shared between code on the server and code installed on each client locally. |
||
| ⚫ | In earlier computing models like client-server, the processing load for the application was shared between code on the server and code installed on each client locally. In other words, an application had its own pre-compiled client program which served as its ] and had to be separately installed on each user's ]. An upgrade to the server-side code of the application would typically also require an upgrade to the client-side code installed on each user workstation, adding to the ] cost and decreasing ]. Additionally, both the client and server components of the application were bound tightly to a particular ] and ], which made ] them to other systems prohibitively expensive for all but the largest applications. | ||
| ⚫ | |||
| ⚫ | Later, in 1995, ] introduced the ] language called ], which allowed programmers to add ] to the user interface that ran on the client side. Essentially, 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 ] 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. .<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 |archive-date=2010-01-07 |archive-url=https://web.archive.org/web/20100107143001/http://java.sun.com/products/servlet/download.html |url-status=dead }}</ref>{{Primary source inline|date=November 2022}} 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.{{Citation needed|date=November 2022|reason=Historical role of Java, ActiveX and later XMLHTTPRequest (which doesn't really have to do anything with XML) should be described using a source. Existing original research is misleading to a point of being useless for someone unfamiliar with the subject.}} | |||
| (Nowadays,<sup>]'']</sup> ] for mobile devices are also hobbled by some or all of the foregoing issues).<sup>] – ]'']</sup> | |||
| Applications like ] started to make their client sides more and more interactive since early 2000s. A web page script is able to contact the server for storing/retrieving data without downloading an entire web page. The practice became known as Ajax in 2005.<ref>{{Cite web |url=https://thehistoryoftheweb.com/what-does-ajax-even-stand-for/ |title=What Does AJAX Even Stand For? |last=Jay Hoffmann |date=2019-03-04 |access-date=2021-10-18 |archive-date=2021-10-18 |archive-url=https://web.archive.org/web/20211018034604/https://thehistoryoftheweb.com/what-does-ajax-even-stand-for/ |url-status=live }}</ref> | |||
| "] |
"]", the term coined by designer Frances Berriman and ] engineer Alex Russell in 2015, refers to apps taking advantage of new features supported by modern browsers, which initially run inside a web browser tab but later can run completely offline and can be launched without entering the app URL in the browser. | ||
| ==Structure== | ==Structure== | ||
Revision as of 04:22, 23 October 2024
Application that uses a web browser as a client
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
A web application (or web app) is application software that is accessed using a web browser. Web applications are delivered on the World Wide Web to users with an active network connection.
Single-page and progressive are two approaches for a website to seem more like a native app.
History
The concept of a "web application" was first introduced in the Java language in the Servlet Specification version 2.2, which was released in 1999. At that time, both JavaScript and XML had already been developed, but the XMLHttpRequest object had only been recently introduced on Internet Explorer 5 as an ActiveX object. Beginning around the early 2000s, applications such as "Myspace (2003), Gmail (2004), Digg (2004), Google Maps (2005)," 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. The practice became known as Ajax in 2005.
In earlier computing models like client-server, the processing load for the application was shared between code on the server and code installed on each client locally. In other words, an application had its own pre-compiled 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-side code of the application would typically also require an upgrade to the client-side code installed on each user workstation, adding to the support cost and decreasing productivity. Additionally, both the client and server components of the application were bound tightly to a particular computer architecture and operating system, which made porting them to other systems prohibitively expensive for all but the largest applications.
Later, in 1995, Netscape introduced the client-side scripting language called JavaScript, which allowed programmers to add dynamic elements to the user interface that ran on the client side. Essentially, 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.
(Nowadays, native apps for mobile devices are also hobbled by some or all of the foregoing issues).
"Progressive web apps", the term coined by designer Frances Berriman and Google Chrome engineer Alex Russell in 2015, refers to apps taking advantage of new features supported by modern browsers, which initially run inside a web browser tab but later can run completely offline and can be launched without entering the app URL in the browser.
Structure
 | This section relies excessively on references to primary sources. Please improve this section by adding secondary or tertiary sources. Find sources: "Web application" – news · newspapers · books · scholar · JSTOR (November 2022) (Learn how and when to remove this message) |
Traditional PC applications are typically single-tiered, residing solely on the client machine. In contrast, web applications inherently facilitate a multi-tiered architecture. 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. 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 does not allow for true specialization of layers, so most applications will outgrow this model.
Security
Main article: Internet security | 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 simplified with the use of web application frameworks. 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.
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.
See also
- D3.js
- Software as a service (SaaS)
- Mobile development framework
- Web 2.0
- Web engineering
- Web GIS
- Web services
- Web sciences
- Web widget
References
- "What Is A Web Application?". stackpath.com. Stack Path. Archived from the original on 2022-08-15. Retrieved 2022-08-15.
A web application is a computer program that utilizes web browsers and web technology to perform tasks over the Internet.
- ^ Petersen, Jeremy (4 September 2008). "Benefits of using the n-tiered approach for web applications". Archived from the original on 1 December 2017. Retrieved 24 November 2017.
- "Top Tips for Secure App Development". Dell.com. Archived from the original on 2012-05-22. Retrieved 2012-06-22.
- Multiple (wiki). "Web application framework". Docforge. Archived from the original on 2020-06-20. Retrieved 2010-03-06.
External links
- HTML5 Draft recommendation, changes to HTML and related APIs to ease authoring of web-based applications.
- Web Applications Working Group at the World Wide Web Consortium (W3C)
- PWAs on Web.dev by Google Developers.
| Web interfaces | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||