HTTP Protocol

Hypertext Transfer Protocol (HTTP) is the core communications protocol used to access the web. Originally developed for retrieving static text, it has been expanded to enable support for more complex applications (Stuttard & Pinto 2011, p.39).
HTTP functions as a request-response protocol between a client and a server, where the client sends a request to the server, and the server returns a response (w3Schools 2016). A HTTP message has both requests and responses. The request takes three items, the HTTP method, the request Uniform Resource Locator (URL) and the HTTP version being used (typically version 1.1).
It is important to understand the errors that can occur with a response, and what they mean in order to rectify the issue. Status messages: 100 series covers information about servers receiving requests, and of asking the server to switch protocols.
200 series covers successful requests, being the request is OK, has been fulfilled, and has been successfully processed.
300 series covers redirection, there can be link lists for the user to select a link, or a link to the page having moved permanently or temporarily.
400 series covers client error, which can be due to syntax error (typo), unauthorised or forbidden request, and the infamous 404 not found.
500 series covers server error, which can be internal, not implemented, unavailable or timed out. (w3Schools 2016)

HTTP methods GET and POST are extremely important as they can affect an applications security if overlooked (Stuttard & Pinot 2011, p.42).
The Get method is used to request data from specified resources. These Get requests remain in the browser history and can be bookmarked, so should not be used with sensitive data – passwords etc. The data is visible to all as it is displayed in the URL (w3Schools 2016).
The Post method is used to submit data to be processed to a specified resource. Post requests should be used when an action is being performed.
Post requests do not remain in the browser and cannot be bookmarked, so is a little safer than Get. No data in displayed in the URL. Data submitted via the Post method will be resubmitted if the user presses the ‘Back’ or ‘reload’ buttons on the browser, it is important to alert the user that the information will be resubmitted (w3Schools 2016).

References
Stuttard D & Pinto M, 2011, The Web Application Hacker’s Handbook, Wiley Publishing, Inc. Indianapolis, Indiana USA.

W3 Schools, 2016, accessed 15th August 2016
http://www.w3schools.com/tags/ref_httpmethods.asp

Full Stack Development

Full stack development combines both front end and back end development. From the highest resolution of the design and interface, to the lowest resolution of bits and bytes. Full stack means developers who are comfortable with front end and back end technology (Fekete 2014). Being a full stack developer does not necessarily mean you need to an expert in both front end and back end. As Pastrana (2015) states, while it is better to specialise in one area, which could be front end or back end code, it is best if you are able to understand enough of the other areas so that you can properly prepare your work to be handed to the person responsible for implementing the next stage. It is also advisable to understand all areas required so you are able to problem solve or at least know who to communicate with about the problem. Being a full stack developer is desirable in start-up and small companies where there may only be one or two developers to create the project, but less common in workplaces that a team to create a project (Fekete 2014).

Front-end development is what the interacting human will see - websites, apps. This includes coding the interface using HTML, CSS and JavaScript.
The back end or server side is hidden from the user. The back end consists of web servers, database, and server side code. Being a full stack developer doesn't mean you have to be an expert in every language. Each individual will have strengths/weaknesses and preferences, it is, however, important to have a solid understanding of each component so to enable proficient communication between the developers in each section (Fekete 2014).
A .NET full stack developer should understand :

ASP.NET stack development

Webpages stack c# + html embedded

Web form ASP

Mvc – model view controller – isolates business logic from the user interface

API – RESTful HTTP services

JSON file – JavaScript object notation

Web app – provides data and the way to display it

Web service – provides data to the browser

References

Fekete G, 22 September 2014, Site Point, accessed 3^rd August 2016

https://www.sitepoint.com/full-stack-developer/ 

Pastrana O, 15 June 2015, Platzi Team, online video, accessed 3^rd August 2016

https://youtu.be/qZb0k4NSzGY 

Dependency Injection

Dependency injection provides the objects that an object needs (dependencies) rather than constructing them itself. Dependency injection uses the dependency inversion principle of code depending upon abstractions (usually an interface) rather than directly depending upon the dependency (Ferrara 2013). A developer no longer needs to instantiate with the new operator from inside of the class. Instead, it can be taken as a constructor parameter or via a setter (Ferrara 2013). Whilst containers are no longer needed with dependency injection, they do make life a lot easier for the developer. Dependency injection containers are a map of dependencies the class needs. The container will also have the logic to create dependencies that haven't been created yet. So instead of creating the classes yourself, you can ask the container for new instances (Ferrara 2013). Dependency injection promotes loose coupling between modules to provide a way to switch code modules being used without the need to build and restart the entire application or parts of it. This could be done by using either a configuration file or by reading dependency injection information from a database table (Jhangra 2016).

 

A benefit of using dependency injection design pattern is that it enables you to ask the container for new instances of a class, saving you from creating them yourself. A developer can also inject additional code between dependencies, for example, validation logic, which saves the developer from having to write this logic for every class. Another benefit of using dependency injection design pattern is that it can make testing a lot easier. Dependency injection allows the developer to replace complex dependencies, such as databases, with mocked implementations of those dependencies, allowing you to isolate the code being tested (Culp 2011).

By using dependency injection, you are able to write cleaner and more efficient code, that is easier to read, easier to test, and easier to modify in the future.

References

Culp A, June 2011, Microsoft, accessed 15^th August 2016

https://msdn.microsoft.com/en-us/library/hh323705(v=vs.100).aspx 

 

Ferrara A, 9 January 2013, online video, accessed 3^rd August 2016

https://youtu.be/IKD2-MAkXyQ 

Jhangra N, 16 June 2016, Code Project, accessed 3^rd August 2016-08-17

http://www.codeproject.com/Articles/1106838/Dependency-Injection-Scenarios-in-Asp-Net-Mvc 

Helpful link

Shimoon A, 14 October 2015, dotnetliberty, online video, accessed 3^rd August

https://youtu.be/5A2UxMGA58g

About me

My name is Kate, I live in Sydney, Australia.
I have a bachelors degree in industrial design and I'm currently studying programming.
My interest in programming sparked when I studied human computer interaction - learning about UI (User Interface) and how to make applications and websites intuitive for the user. Already competent in graphical components, I was interested in how the back end worked.
My hobbies include travelling, cooking, reading, and watching movies and TV.