Monday, October 24, 2011

Week 7- Networks


Inevitably, my restaurant will have a website. What is a restaurant today without an accompanied website with its menu, location, contact information, etc? The website will have its domain name, probably the name of the restaurant, but really what that is is the IP address. In order for the website to communicate it needs the IP address. Also, the organization ICANN will have to approve my domain name because it regulates and approves all the domain names on the internet.
Relating back to week one with social media, more specifically twitter- I discussed how I would tweet daily about deals, specials, and different incentives to get more business. All of this wouldn’t be possible without packets and protocols. Packets are a small chunk of information, typically part of a larger piece of information. My tweets will be sent to the twitter database in packets, and as a result be posted for all of my followers to see.
Another piece of vital information that will make my website function is the use of protocols. A protocol is rules of communication including syntax and semantics. A common web protocol that virtually everyone knows about, but doesn’t know its purpose is HTTP (hypertext transfer protocol). Every website begins with HTTP and is followed by the domain name. Without the HTTP, however, the website wouldn’t function. It is a four step process between the client (the website) and the web server (a running application that hosts the website). I would submit an HTTP request message to the server, and in return I get a response from the server. The response would contain the completion status information about the request in addition to the information requested- in this case the information within the website. 
The technicalities behind the website are difficult to understand, however, they are essential in creating a website that would help business. 

No comments:

Post a Comment