Share
VIDEOS 1 TO 50
Basic concepts of web applications, how they work and the HTTP protocol
Basic concepts of web applications, how they work and the HTTP protocol
Published: 2014/07/27
Channel: Natural Programmer
Key Differences Between a Web Application and a Website
Key Differences Between a Web Application and a Website
Published: 2016/03/08
Channel: Mode Effect
Websites  vs WebApps
Websites vs WebApps
Published: 2016/03/07
Channel: IT India
Web Architecture Basics
Web Architecture Basics
Published: 2017/02/26
Channel: Dave Xiang
I Designed, Coded & Launched A Web App in 24 Hours [Vlog 001]
I Designed, Coded & Launched A Web App in 24 Hours [Vlog 001]
Published: 2016/02/21
Channel: Mackenzie Child
How To Make A Web App In 7 Minutes
How To Make A Web App In 7 Minutes
Published: 2013/05/04
Channel: Tinkernut
Web Applications - Web Development
Web Applications - Web Development
Published: 2014/06/03
Channel: Udacity
Web pages, Websites, and Web Applications
Web pages, Websites, and Web Applications
Published: 2016/05/05
Channel: WebDev Cave
Websites vs Web Applications pt 1 - Know the Difference
Websites vs Web Applications pt 1 - Know the Difference
Published: 2016/07/15
Channel: Mode Effect
Why Build Progressive Web Apps?
Why Build Progressive Web Apps?
Published: 2017/04/26
Channel: Google Chrome Developers
React.js: Super-fast Single Page Web Applications
React.js: Super-fast Single Page Web Applications
Published: 2016/01/04
Channel: Parleys
Chrome Web Store - What
Chrome Web Store - What's a web app?
Published: 2010/12/06
Channel: Google Chrome
Introduction to Web Application Servers
Introduction to Web Application Servers
Published: 2014/11/06
Channel: Mike Murphy
ASP.NET: Building Web Application Using ASP.NET and Visual Studio
ASP.NET: Building Web Application Using ASP.NET and Visual Studio
Published: 2014/05/20
Channel: TechEd North America
Building a Web App From Scratch With AngularJS: Introduction
Building a Web App From Scratch With AngularJS: Introduction
Published: 2014/09/29
Channel: Envato Tuts+
Web application vs Enterprise application
Web application vs Enterprise application
Published: 2014/08/23
Channel: Durga Software Solutions
Firebase Web App Tutorial - Basics - Introduction / Adding Data to Database [ Part 1 ]
Firebase Web App Tutorial - Basics - Introduction / Adding Data to Database [ Part 1 ]
Published: 2016/09/07
Channel: TVAC Studio
Creating a web database application in 5 minutes using AppGini
Creating a web database application in 5 minutes using AppGini
Published: 2015/01/19
Channel: AppGini -- Web applications in minutes!
Introduction to Web Application Development
Introduction to Web Application Development
Published: 2014/01/03
Channel: senturain
Web application architecture: The whole stack - Allen Holub
Web application architecture: The whole stack - Allen Holub
Published: 2015/05/08
Channel: DevWeek Events
Why Build a Progressive Web App?
Why Build a Progressive Web App?
Published: 2016/08/08
Channel: Udacity
10. Build a Web App - Step 1 - MySQL/PHP
10. Build a Web App - Step 1 - MySQL/PHP
Published: 2014/03/18
Channel: DesignCourse
How to Develop Web Application using pure Node.js (HTTP GET and POST, HTTP Server)
How to Develop Web Application using pure Node.js (HTTP GET and POST, HTTP Server)
Published: 2015/08/07
Channel: Tech CBT
Introduction to Web Application Firewalls
Introduction to Web Application Firewalls
Published: 2016/01/12
Channel: Symantec + Blue Coat
THE START!!! WEB APP LAUNCH!! PACKS!! SBCs!!! OMG!!  - Poor Man RTG #1 - FIFA 18 Ultimate Team
THE START!!! WEB APP LAUNCH!! PACKS!! SBCs!!! OMG!! - Poor Man RTG #1 - FIFA 18 Ultimate Team
Published: 2017/09/20
Channel: Nick28T
Create An Access 2013 Web App From Scratch
Create An Access 2013 Web App From Scratch
Published: 2014/07/30
Channel: Access All In One
Testing Web Applications
Testing Web Applications
Published: 2017/04/27
Channel: LearnForIndians
Creating a Web Application with Eclipse IDE
Creating a Web Application with Eclipse IDE
Published: 2012/02/01
Channel: Shoaib Khan
đŸ’„ Angular and Firebase 3 - Build a Web Application - 1h Course Sample
đŸ’„ Angular and Firebase 3 - Build a Web Application - 1h Course Sample
Published: 2016/10/07
Channel: Angular University
Web Server vs  Application Server
Web Server vs Application Server
Published: 2014/08/23
Channel: Durga Software Solutions
Web Application Security Demo
Web Application Security Demo
Published: 2010/10/07
Channel: Imperva
Database Driven Web Application in less than 5 minutes Using Visual Studio
Database Driven Web Application in less than 5 minutes Using Visual Studio
Published: 2010/11/22
Channel: PrH1ndo
Part 3 - Creating Web Application - SharePoint 2013 Tutorial
Part 3 - Creating Web Application - SharePoint 2013 Tutorial
Published: 2014/08/08
Channel: BestDotNetTraining
Make Java Web Application Connect To MySQL
Make Java Web Application Connect To MySQL
Published: 2015/12/21
Channel: IntoProgram
How to create a new Web App | Azure App Service
How to create a new Web App | Azure App Service
Published: 2015/05/27
Channel: Azure App Service
Firebase Web Application Chat
Firebase Web Application Chat
Published: 2016/12/31
Channel: Robert Soriano
FIFA 18 WEB APP!
FIFA 18 WEB APP!
Published: 2017/09/20
Channel: MattHDGamer
Troubleshooting Live Java Web Applications
Troubleshooting Live Java Web Applications
Published: 2013/11/13
Channel: SpringDeveloper
Creating a .NET Core 1.1 MVC Web Application from scratch - Part 1 - Adding MVC to an Empty Project
Creating a .NET Core 1.1 MVC Web Application from scratch - Part 1 - Adding MVC to an Empty Project
Published: 2016/11/17
Channel: Arhnuld
Introduction to web application frameworks
Introduction to web application frameworks
Published: 2013/09/17
Channel: Philip Johnson
SharePoint 2013 - Creating a Web Application & Site Collection
SharePoint 2013 - Creating a Web Application & Site Collection
Published: 2013/03/27
Channel: Pluralsight IT - Training Archive
How to turn a spreadsheet into a database-driven web application
How to turn a spreadsheet into a database-driven web application
Published: 2014/03/26
Channel: The m-Power Platform
Create a Single Page Web Application using C#
Create a Single Page Web Application using C#
Published: 2014/01/19
Channel: zeidrizvic1
Drupal web application example: Travel Planner
Drupal web application example: Travel Planner
Published: 2014/11/24
Channel: Andy Inman
Web Application Performance 101
Web Application Performance 101
Published: 2013/06/14
Channel: John Spirko
Deploying a Google Apps Script Web Application PART 1
Deploying a Google Apps Script Web Application PART 1
Published: 2017/07/18
Channel: Jordan Rhea
100 OWASP Top 10 Hacking Web Applications with Burp Suite Chad Furman
100 OWASP Top 10 Hacking Web Applications with Burp Suite Chad Furman
Published: 2017/06/16
Channel: Adrian Crenshaw
MVC web application JAVA Tutorial
MVC web application JAVA Tutorial
Published: 2012/10/26
Channel: ZA JAVA Web Development
Developing Java Web Application Part 1 | Advanced Java Tutorial | Mr. Nataraj
Developing Java Web Application Part 1 | Advanced Java Tutorial | Mr. Nataraj
Published: 2016/12/13
Channel: Naresh i Technologies
Integrating Power BI Into Your Web Applications
Integrating Power BI Into Your Web Applications
Published: 2016/09/15
Channel: Microsoft Visual Studio
NEXT
GO TO RESULTS [51 .. 100]

WIKIPEDIA ARTICLE

From Wikipedia, the free encyclopedia
  (Redirected from Web applications)
Jump to: navigation, search
Horde groupware is an open-source web application.

In computing, a web application or web app is a client–server computer program in which the client (including the user interface and client-side logic) runs in a web browser.[1] Common web applications include webmail, online retail sales, online auctions, wikis, instant messaging services and many other functions.

Definition and similar terms[edit]

The general distinction between a dynamic web page of any kind and a "web application" 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 mobile app. HTML5 introduced explicit language support for making applications that are loaded as web pages, but can store data locally and continue to function while offline.

Single-page applications are more application-like because they reject the more typical web paradigm of moving between distinct pages with different URLs. Single-page frameworks like Sencha Touch and AngularJS might be used to speed development of such a web app for a mobile platform.

Mobile web applications[edit]

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

  • Responsive web design can be used to make a web application - whether a conventional web site or a single-page application viewable on small screens and work well with touchscreens.
  • Progressive Web Apps are a hybrid of regular web pages (or websites) and a mobile application.
  • Native apps or "mobile apps" run directly on a mobile device, just as a conventional software application runs directly on a desktop computer, without a web browser (and potentially without the need for Internet connectivity); these are typically written in Java (for Android devices) or Objective C or Swift (for iOS devices). Recently, frameworks like React Native, Flutter and Xamarin allow the development of native apps for all platforms using languages other than each standard native language.
  • Hybrid apps embed a mobile web site inside a native app, possibly using a hybrid framework like Apache Cordova and Ionic or Appcelerator Titanium. 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).

History[edit]

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. In addition, both the client and server components of the application were usually tightly bound to a particular computer architecture and operating system and porting them to others was often prohibitively expensive for all but the largest applications. (Today, of course, native apps for mobile devices are also hobbled by some or all of the foregoing issues.)

In contrast, web applications use web documents written in a standard format such as HTML and JavaScript, which are supported by a variety of web browsers. Web applications can be considered as a specific variant of client–server software where the client software is downloaded to the client machine when visiting the relevant web page, using standard procedures such as HTTP. Client web software updates may happen each time the web page is visited. During the session, the web browser interprets and displays the pages, and acts as the universal client for any web application.

In the early days of the Web, each individual web page was delivered to the client as a static document, but the sequence of pages could still provide an interactive experience, as user input was returned through web form elements embedded in the page markup. However, every significant change to the web page required a round trip back to the server to refresh the entire page.

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 1996, Macromedia introduced Flash, a vector animation player that could be added to browsers as a plug-in 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?].[2][3] 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.[4]

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.

In 2011, HTML5 was finalized, which provides graphic and multimedia capabilities without the need of client side plug-ins. HTML5 also enriched the semantic content of documents. The APIs and document object model (DOM) are no longer afterthoughts, but are fundamental parts of the HTML5 specification. WebGL API paved the way for advanced 3D graphics based on HTML5 canvas and JavaScript language. These have significant importance in creating truly platform and browser independent rich web applications.

Interface[edit]

Through Java, JavaScript, DHTML, Flash, Silverlight 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. Recently, technologies have been developed to coordinate client-side scripting with server-side technologies such as ASP.NET, J2EE, Perl/Plack and PHP.

Ajax, a web development technique using a combination of various technologies, is an example of technology which creates a more interactive experience.

Structure[edit]

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 an 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, 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).[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 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.[5] 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.[5] 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.[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]

Business use[edit]

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.

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.[6] 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.

Cloud Computing model web applications are software as a service (SaaS). There are business applications provided as SaaS for enterprises for fixed or usage dependent fee. Other web applications are offered free of charge, often generating income from advertisements shown in web application interface.

Development[edit]

Writing a web application is often simplified by open source software[relevant? ] such as Django, Ruby on Rails or Symfony called 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.[7] While many of these frameworks are open source, this is by no means a requirement.

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[8] such as GET after POST.

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.

Applications[edit]

Examples of browser applications are simple office software (word processors, online spreadsheets, and presentation tools), but can also include more advanced applications such as project management, computer-aided design, video editing and point-of-sale.

See also[edit]

References[edit]

  1. ^ Nations, Daniel. "Web Applications". About.com. Retrieved 20 January 2014. 
  2. ^ Alex Chaffee (2000-08-17). "What is a web application (or "webapp")?". Retrieved 2008-07-27. 
  3. ^ James Duncan Davidson, Danny Coward (1999-12-17). Java Servlet Specification ("Specification") Version: 2.2 Final Release. Sun Microsystems. pp. 43–46. Retrieved 2008-07-27. 
  4. ^ "Dynamic HTML and XML: The XMLHttpRequest Object". Apple Inc. Retrieved 2008-06-25. 
  5. ^ a b c d e f g h i j Jeremy Petersen. "Benefits of using the n-tiered approach for web applications". 
  6. ^ "Top Tips for Secure App Development". Dell.com. Retrieved 2012-06-22. 
  7. ^ Multiple (wiki). "Web application framework". Docforge. Retrieved 2010-03-06. 
  8. ^ Multiple (wiki). "Framework". Docforge. Retrieved 2010-03-06. 

External links[edit]

Disclaimer

None of the audio/visual content is hosted on this site. All media is embedded from other sites such as GoogleVideo, Wikipedia, YouTube etc. Therefore, this site has no control over the copyright issues of the streaming media.

All issues concerning copyright violations should be aimed at the sites hosting the material. This site does not host any of the streaming media and the owner has not uploaded any of the material to the video hosting servers. Anyone can find the same content on Google Video or YouTube by themselves.

The owner of this site cannot know which documentaries are in public domain, which has been uploaded to e.g. YouTube by the owner and which has been uploaded without permission. The copyright owner must contact the source if he wants his material off the Internet completely.

Powered by YouTube
Wikipedia content is licensed under the GFDL and (CC) license