WAD 1
Task 1 –
Functions and Advantages of Web Applications
Stuttard, 2008, states that the majority of websites online currently are actually in-fact applications, as they are dynamic and rely on a two-way flow of information and interactivity/interaction between the server and the client. This in stark contrast to the early days of the web, when websites mostly consisted of HTML pages containing static information. Many of the functions one might associate with the modern Internet are in-fact conducted by applications:
Common Web Application Functions
User Authentication: It is important to be able to authenticate users accessing web services. This is for a several reasons, such as security/data protection and providing a personalised service. There are several mechanisms in which this can be accomplished, such as a webserver validating the client machine through their IP address/digital certificates/cookies etc. Another, perhaps more familiar method for user authentication would be the use of login credentials (usernames and passwords etc). To perform this, web applications must provide:
Information Storage and Recall: Although traditional web pages can be great providers of information, often the amounts of data required may be too large to be feasibly placed directly in an HTML document. Additionally, all data/information stored on a website may not be relevant to most users, and they it’s likely they may only require a small portion of it. Confidentiality of data can be important too, which is why the aforementioned user authentication functions of web applications can prove so beneficial. Finally, authorised users may need to add, edit or remove information from a website; in a static HTML document, potential laypeople could be expected to directly edit source-code. Things such as forums, guestbooks and login systems all rely on this information storage, recall and manipulation. Relational databases are often a good solution to this need, and web applications
Functions and Advantages of Web Applications
Stuttard, 2008, states that the majority of websites online currently are actually in-fact applications, as they are dynamic and rely on a two-way flow of information and interactivity/interaction between the server and the client. This in stark contrast to the early days of the web, when websites mostly consisted of HTML pages containing static information. Many of the functions one might associate with the modern Internet are in-fact conducted by applications:
Common Web Application Functions
User Authentication: It is important to be able to authenticate users accessing web services. This is for a several reasons, such as security/data protection and providing a personalised service. There are several mechanisms in which this can be accomplished, such as a webserver validating the client machine through their IP address/digital certificates/cookies etc. Another, perhaps more familiar method for user authentication would be the use of login credentials (usernames and passwords etc). To perform this, web applications must provide:
Information Storage and Recall: Although traditional web pages can be great providers of information, often the amounts of data required may be too large to be feasibly placed directly in an HTML document. Additionally, all data/information stored on a website may not be relevant to most users, and they it’s likely they may only require a small portion of it. Confidentiality of data can be important too, which is why the aforementioned user authentication functions of web applications can prove so beneficial. Finally, authorised users may need to add, edit or remove information from a website; in a static HTML document, potential laypeople could be expected to directly edit source-code. Things such as forums, guestbooks and login systems all rely on this information storage, recall and manipulation. Relational databases are often a good solution to this need, and web applications
References: AQTRONIX. (2015). AQTRONIX WebKnight - Open Source Web Application Firewall (WAF) for IIS. Retrieved 20th May 2015, from http://www.aqtronix.com/?PageID=99 Provos et al ISO (2008). ISO/IEC 9075-1:2008. Retrieved 20th May 2015, from http://www.iso.org/iso/catalogue_detail.htm?csnumber=45498 Parekh et al Christoff Kern, 2014: http://search.ebscohost.com/login.aspx?direct=true&AuthType=ip,cookie,url,uid&db=bch&AN=97638726&site=ehost-live&user=ns004994&password=RFq52nap