<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/platform.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d458238135907614700\x26blogName\x3dMary\x27s+NET11+Blog\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dBLUE\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttps://net-studies.blogspot.com/search\x26blogLocale\x3den_US\x26v\x3d2\x26homepageUrl\x3dhttp://net-studies.blogspot.com/\x26vt\x3d-8627547258479053563', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Mary's NET11 Blog

This blog is in the form of a 'learning log' for my online studies @ Curtin for NET11.

Saturday Reflections (Part I )

Saturday, March 3, 2007

Every Saturday I'll give my weekly reflections on my study of NET11.



After reading the recommended links 'The Basic Process' and 'The Internet' on HowStuffWorks.com I couldn't help but compare some of the Internet protocols to my part-time work as a waitress at a restaurant. I'll draw a little cartoon to explain.



A waitress acts like our web browser.





So the waitress is the web browser, being the 'middle-man' for the customer, and from the customers point of view, that is all they want, 2 simple steps -


1) order the food (type in the URL)


2) receive the food (view the web page)


However once the waitress or browser has the order/page request, the part of the process that the customer doesn't see happens.

  • The waitress assigns table number and order to customer (The URL is sent to a name server to turn the basic name into an IP address.)

  • Once the table number and order are assigned, the order can be put through to the kitchen. (The browser connects to the server at that IP address.)

  • The kitchen receives the order, and starts cooking the requested food on the order. (The browser follows the HTTP protocol to send a GET request to the server, asking for the specific file.)

  • The kitchen sends the food out, ready to serve. (The server sends the HTML text for the web page to the browser.)

  • Waitress checks for table number and delivers food to the table. (The browser reads the HTML tags and shows the page on your screen.) 1
- Mary



Reference List

In the above bulleted list, the Internet information is referenced from -
1 Brain, M. Behind the Scenes: How Web Servers Work, Retrieved March 3, 2007, from the How Stuff Works Websitehttp://computer.howstuffworks.com/web-server2.htm

Labels: ,

leave a comment