The following is a brief description of the internet’s various components.
The following sections will not discuss the technical aspects of the various components of the network; they will discuss the general principles and practices that govern how the internet works.
For more detailed information on the various internet components and their use, see Wikipedia’s article on the internet.
A quick introduction To get an idea of what is happening on the net, let’s take a look at how things work.
When you download a file from an internet service provider, the provider sends it to a server, usually a server in a country where it can’t be accessed by most of the population.
A server in Canada sends the file to a US server that is not accessible by most Canadians, or an Australian server that can only reach Australia and New Zealand.
In a few cases, a server from a particular country sends files to a particular server in the US, which forwards them to a specific US server.
These connections between servers are known as “peering”.
The US servers use the IP addresses of the US servers to identify themselves, but they also know which countries their peers are.
The US peers use the same IP addresses as the Canadian servers and vice versa.
The Canadian peers can also send traffic to each other.
When a Canadian or an American peers a peer from a different country, the Canadian or the American peers send a request to the Canadian server.
This request contains information about the peer, including the country in which it resides, a list of the peers, and a list and description of all of the peer’s resources.
If the request is successful, the peer then responds with the list of all the resources that it has.
The server in each country has to reply to the request with information about what it has to send back.
The servers in each nation use this information to determine which peer has the requested resource, and then determine which resource should be forwarded.
The information sent back is also referred to as “request headers”.
The request headers are used to establish the peer-to-peer connection.
Once the peer receives the request, it replies with a request for more information.
The request for information consists of a list (or “set”) of information that the peer needs to respond to the server, including: The country in the list the peer is located in.
The name of the country.
The IP address of the server.
The list of peer resources, such as files and images.
If you have an image that you want to share, it might be stored on the server in that country, and the server may send the request for a file that can be shared.
The requested file, if any, can then be uploaded to the peer in that other country.
For example, the request headers might include: Request ID: 0x2024 Request Time: 0:52:03:16:24:0 Content Type: image/jpeg (size: 11,16 KB) Request Header: Content-Type: application/octet-stream Request Content-Length: 0 Request Body: Request Body Length: 0 The server responds with a list, which is called a “header”.
It contains information that is usually sent to all other requests to the same server.
Each request is a unique set of data.
This unique set is called the “request body”.
Each request also contains a “set of headers”, which are a set of bits in the request body that are used by the server to determine the requested resources.
The set of headers contains a set and set of information about every resource that the server has to respond with.
The headers can contain: The request body itself, such it contains the request header, or a set header with additional information that describes how the server responded.
The header headers may contain: Resource ID: This is the resource ID, which identifies the resource.
For file sharing, a file is an IP address.
For browsing, it may contain the file’s name.
Resource Type: The resource type is used to identify what kind of resource this resource is.
If it is a file, it is an image file, or if it is another resource, it’s a list.
Resource Identifier: The identifier is used in a “proxy” request to tell the server what kind, or type of resource the resource is (for example, if a file resource is a directory).
For example: Proxy Server: https://proxy.yourdomain.com/res/download.html Proxy: http://proxy1.yourserver.com/?proxy=yourdomain Proxy: /res/Download.html Response Header: This header describes the response from the server (for file sharing) or the request that it received (for browsing).
For more information about header information, see RFC 2701.
The response to a proxy request is called “headers”.
The headers may be small files or, sometimes