Web Hosting :-

Types of Web Hosting :-

Free Hosting

Some service providers offer free web hosting.
Free web hosting is best suited for small sites with low traffic, like family sites or sites about hobbies. It is not recommended for high traffic or for real business. Technical support is often limited, and technical options are few.
Very often you cannot use your own domain name at a free site. You have to use a name provided by your host like http://www.freesite/users/~yoursite.htm. This is hard to type, hard to remember, and not very professional.

Shared (Virtual) Hosting

Shared hosting is very common, and very cost effective.
With shared hosting, your web site is hosted on a powerful server along with maybe 100 other web sites. On a shared host it is common that each web site have their own domain name.
Shared solutions often offer multiple software solutions like email, database, and many different editing options. Technical support tends to be good.

Good:	Bad:
Low cost. Cost is shared with others.	Reduced security due to many sites on one server.
Good for small business and average traffic.	Restrictions on traffic volume.
Multiple software options.	Restricted database support.
Own domain name.	Restricted software support.
Good support

Dedicated Hosting

With dedicated hosting your web site is hosted on a dedicated server.
Dedicated hosting is the most expensive form of hosting. The solution is best suited for large web sites with high traffic, and web sites that use special software.
You should expect dedicated hosting to be very powerful and secure, with almost unlimited software solutions.

Good:	Bad:
Good for large business.	Expensive.
Good for high traffic.	Requires higher skills.
Multiple domain names.
Powerful email solutions.
Powerful database support.
Strong (unlimited) software support.

Collocated Hosting

Collocation means "co-location". It is a solution that lets you place (locate) your own web server on the premises (locations) of a service provider.
This is pretty much the same as running your own server in your own office, only that it is located at a place better designed for it.
Most likely a provider will have dedicated resources like high-security against fire and vandalism, regulated backup power, dedicated Internet connections and more.

Good:	Bad:
High bandwidth.	Expensive.
High up-time.	Requires higher skills.
High security.	Harder to configure and debug.
Unlimited software options

Multi Homing :-

Multi-homing is a situation that describes a single computer host that makes use of several IP addresses associated with various connected networks. Within this scenario, the multihomed computer host is physically linked to a variety of data connections or ports. These connections or ports may all be associated with the same network or with a variety of different networks. Depending on the exact configuration, multi-homing may allow a computer host to function as an IP router.
The process of multi-homing makes use of what is known as Stream Control Transmission Protocol, or SCTP. Essentially, the process involves employing multi-homing by making use of a single SCTP endpoint to support the connectivity to more than one IP address. By establishing connection to multiple addresses, multi-homing can help to enhance the overall stability of the connectivity associated with the host.
One of the advantages of multi-homing is that the computer host is somewhat protected from the occurrence of a network failure. With systems that make use of a single IP address and connection, the failure of the connected network means that the connection shuts down, rendering the end system ineffectual as far as connectivity to the Internet is concerned. With multi-homing, the failure of a single network only closes a single open door. All the other doors, or IP addresses associated with the other networks, remain up and functional. 

In general, multi-homing is helpful for three elements of effective web management. First, multi-homing can help to distribute the load balance of data transmissions received and sent by the computer host. Second, the redundancy that is inherent to multi-homing means less incidences of downtime due to network failure. Last, multi-homing provides an additional tool to keep network connectivity alive and well in the event of natural disasters or other events that would normally render a host inoperative for an extended period of time. 

Document Root

The document root is the server path that is accessible by web visitors and robots.  While it can be the server root, it is commonly set as a secondary directory such as public_html.  There is nothing special about this name and the directory which it is set varies from web server to web server.  Please consult with your systems administrator, virtual domain host, or server documentation if you are not sure what your document root is.

The document root is a directory (a folder) that is stored on your host's servers and that is designated for holding web pages. When someone else looks at your web site, this is the location they will be accessing.
In order for a website to be accessible to visitors, it must be published to the correct directory, the "document root."
You might think that there would only be one directory in your space on your host's servers, but often hosts provide services beyond just publishing a website. In this case, they are likely to set up every account with several directories, since each service would require its own.
If you log into your host you might see a number of directories as shown below:

Remember, every host is different, so yours will probably not look exactly like the picture above. Yours is quite likely to have a completely different set of folders. It might even have none.
In the example shown above, the document root is the "www" directory, but of course your host may well use a different folder. Some of the more common alternatives are:

• htdocs
• httpdocs
• html
• public_html
• web

Your host may even have several folders nested inside each other, one of which is the document root. In the example above the document root was:

/www/

but your host may use something like one of these:

/web/public/

/example.com/www/public/

/example.com/public_html/

Quite simply there is no way we at Karelia can know for sure what your document root is. Your host's technical support should have sent you this information when your first signed up for their services. If necessary, please contact them to find out your document root.
To further complicate matters, not all hosts refer to this folder as the document root! They might instead call it:

• Start directory
• Home directory
• Web publishing directory
• Remote root