How Bout The Internet

Ok, here is a quick snopsis of what I have learned from that site: The internet works like this: 1. You open up your web browser. THe browser is software that interperts and communicates with the internet 2. You type in http://www.google.com/imghp?:80 http:// is the protocol and means that you are trying to access that type of webpage www.google.com is the host name. When the computer looks for the webpage, it looks for www.google.com /imghp? is a different branch in the google.com directory tree. :80 is the port the computer needs to use to connect to the website. If you dont put it (which noone does) then the computer uses the default port, port 80. So what does the browser do with all of this information? Well, the computer doesn't know what www.google.com is. It is used to ip addresses. The computer thinks of www.google.com as [removed] But, as people, it is much easier for us to remember www.google.com than 64.233.167.104 Sooo, we use a converter. When we type in www.google.com the computer looks in different places to find the translation. (the translator is called domain name server.) first it looks at the hosts file on your computer. If it is not there, then the computer asks your isp's domain name server for the corresponding ip address. If the isp's server doesnt know, then the isp's domain server asks the root server where it can find it. THe root server is the server that oversees all of the servers that host ip address converters. ONce the isp's server finds out which server to talk to, it can get the dns translation. google's server tells your isp's server the correct translation. Then the isp's server gives the information to your computer. The computer also looks at the protocol (http:// in this instance) When the computer connects to google.com, it knows what "language" to talk in. It's like there being a sign that says "speak english here" and "speak french here" so that you know when to speak english and when to speak french. Now, your computer knows the ip address, and the protocol to talk to google's server. The port number tells the computer which port to talk from. Once your computer does all of this, a direct connection is placed between your computer and google's server using the http:// protocol and communicating through port 80 on your computer. (more to come later… Im sick of typing right now wng

wng_z3r0, great job! Ever run tracert in the command prompt? That what I like to see, the PC trying to find its way to www.google.com or where ever you want to go. It's also what determines what your response time will be like in playing games. Recently I was reading some material at a site that had a bit of misinformation there. There are 2 factors controling ping or response time most which you have no control over. This was a big factor for me since I play FPS games that milisecond means the difference between living or dying. You will find alot of software and tweaks around claiming they can improve your ping. That is simply not true. Reason is no one can control #1 the speed of electricity, its speed is a constant relative directly to ping amd number of hops. #2 The hop or route you will take. No one can control if all the hops will be responding correctly be too busy or some tech trips over a cable and disconnects that machine from the route…. Another false statement I see a lot is 56k vs cable or DSL. My 56k dial up was faster in time getting to the west coast game servers than my 4Mbit cable is. Simply the 56k took 5 less hops to get to the same place than my cable. For some reason my cable takes 5 hops bouncing around the Island before it heads to LA. Weird. My 56k took one from my house to Hawaiian Tels relay then right to LA and a few more to the server.