Welcome to www.taxkingsandqueens.com
|
Web Hosting - The Internet and How It Works
In one sense, detailing the statement in the title would require at least a book. In another sense, it can't be fully explained at all, since there's no central authority that designs or implements the highly distributed entity called The Internet.
But the basics can certainly be outlined, simply and briefly. And it's in the interest of any novice web site owner to have some idea of how their tree fits into that gigantic forest, full of complex paths, that is called the Internet.
The analogy to a forest is not far off. Every computer is a single plant, sometimes a little bush sometimes a mighty tree. A percentage, to be sure, are weeds we could do without. In networking terminology, the individual plants are called 'nodes' and each one has a domain name and IP address. Connecting those nodes are paths.
The Internet, taken in total, is just the collection of all those plants and the pieces that allow for their interconnections - all the nodes and the paths between them.
Servers and clients (desktop computers, laptops, PDAs, cell phones and more) make up the most visible parts of the Internet. They store information and programs that make the data accessible. But behind the scenes there are vitally important components - both hardware and software - that make the entire mesh possible and useful.
Though there's no single central authority, database, or computer that creates the World Wide Web, it's nonetheless true that not all computers are equal. There is a hierarchy. That hierarchy starts with a tree with many branches: the domain system.
Designators like .com, .net, .org, and so forth are familiar to everyone now. Those basic names are stored inside a relatively small number of specialized systems maintained by a few non-profit organizations. They form something called the TLD, the Top Level Domains. From there, company networks and others form what are called the Second Level Domains, such as Microsoft.com.
That's further sub-divided into www.Microsoft.com which is, technically, a sub-domain but is sometimes mis-named 'a host' or a domain. A host is the name for one specific computer. That host name may or may not be, for example, 'www' and usually isn't. The domain is the name without the 'www' in front. Finally, at the bottom of the pyramid, are the individual hosts (usually servers) that provide actual information and the means to share it.
Those hosts (along with other hardware and software that enable communication, such as routers) form a network. The set of all those networks taken together is the physical aspect of the Internet.
There are less obvious aspects, too, that are essential. When you click on a URL (Uniform Resource Locator, such as http://www.microsoft.com) on a web page, your browser sends a request through the Internet to connect and get data. That request, and the data that is returned from the request, is divided up into packets (chunks of data wrapped in routing and control information).
That's one of the reasons you will often see your web page getting painted on the screen one section at a time. When the packets take too long to get where they're supposed to go, that's a 'timeout'. Suppose you request a set of names that are stored in a database. Those names, let's suppose get stored in order. But the packets they get shoved into for delivery can arrive at your computer in any order. They're then reassembled and displayed.
All those packets can be directed to the proper place because they're associated with a specified IP address, a numeric identifier that designates a host (a computer that 'hosts' data). But those numbers are hard to remember and work with, so names are layered on top, the so-called domain names we started out discussing.
Imagine the postal system (the Internet). Each home (domain name) has an address (IP address). Those who live in them (programs) send and receive letters (packets). The letters contain news (database data, email messages, images) that's of interest to the residents.
The Internet is very much the same.
How to copyright music How to Copyright Music for the Beginner For those wondering how to copyright music the answer can be both long and short. The first thing to remember is that most people are confused about exactly what it means to actually copyright music. Music is actually copyrighted as soon as it is presented in a fixed form. It doesn't really matter whether that fixed form is as written sheet music or as a recording. Most people are looking for solid legal protection and while a copyright is good to have, it is essentially worthless unless you've actually gone to the effort of also registering your copyright. Rather than asking 'how to copyright music', perhaps the better question would be 'what do I do now that I've copyrighted my music?' It doesn't really matter what you call it unless you're moving around in legal or industry circles I suppose, but I've always felt that it's a good idea to have a clue about the process in which you are embarking. Now that we've answered how to copyright music, it's time to move on to the real issue, which is registering your copyright. Music is registered through the U. S. Copyright Office. You will need to fill out an application, pay a fee, and provide a copy of your music. As far as government dealings go, this is one of the least painful. Even the fee is marginal when you consider your 'hopeful' future profits and royalties. All that aside, there is something that is massively satisfying about knowing how to copyright music and having your first piece of music registered. Music is an art form and the ability to write music is nothing insignificant. It is a real talent that is actually quite rare. Many popular musicians today use music that has been written by others either in addition to or rather than music that they have written themselves. Even if you aren't a talented performer, it doesn't mean that your music will never be seen or heard or that you should not bother learning how to copyright music. You just might find that you are more in demand for your particular talents than you would have ever dreamed possible. The big thing to remember though is not to sit around wondering how to copyright music but to get out there and go about the process of creating and making more wonderful music to share with the world. It takes all kinds of music to keep this world turning and there is someone out there that is waiting to hear the music that you create. The process of how to copyright music is completely free. The process of registering your copyright is worth every penny you will spend. It is important to protect your music now more than ever with piracy and widespread downloading providing significant reductions in profits for everyone involved. The music industry is also a very fickle industry and you need to maximize your profit potential and usefulness. Once you understand how to copyright music, you need to make sure every piece of music you have has been copyrighted, then you need to go through your music and systematically register each and every piece as well. Even if you must do one piece at a time until you manage to register the copyright on them all, it is much better to be safe than sorry should you ever go to trial in a copyright infringement case. Also remember to pay it forward and support up and coming musicians by sharing the information of how to copyright music and how to register copyrights as well. Web Hosting - Sharing A Server – Things To Think About You can often get a substantial discount off web hosting fees by sharing a server with other sites. Or, you may have multiple sites of your own on the same system. But, just as sharing a house can have benefits and drawbacks, so too with a server. The first consideration is availability. Shared servers get re-booted more often than stand alone systems. That can happen for multiple reasons. Another site's software may produce a problem or make a change that requires a re-boot. While that's less common on Unix-based systems than on Windows, it still happens. Be prepared for more scheduled and unplanned outages when you share a server. Load is the next, and more obvious, issue. A single pickup truck can only haul so much weight. If the truck is already half-loaded with someone else's rocks, it will not haul yours as easily. Most websites are fairly static. A reader hits a page, then spends some time skimming it before loading another. During that time, the server has capacity to satisfy other requests without affecting you. All the shared resources - CPU, memory, disks, network and other components - can easily handle multiple users (up to a point). But all servers have inherent capacity limitations. The component that processes software instructions (the CPU) can only do so much. Most large servers will have more than one (some as many as 16), but there are still limits to what they can do. The more requests they receive, the busier they are. At a certain point, your software request (such as accessing a website page) has to wait a bit. Memory on a server functions in a similar way. It's a shared resource on the server and there is only so much of it. As it gets used up, the system lets one process use some, then another, in turn. But sharing that resource causes delays. The more requests there are, the longer the delays. You may experience that as waiting for a page to appear in the browser or a file to download. Bottlenecks can appear in other places outside, but connected to, the server itself. Network components get shared among multiple users along with everything else. And, as with those others, the more requests there are (and the longer they tie them up) the longer the delays you notice. The only way to get an objective look at whether a server and the connected network have enough capacity is to measure and test. All systems are capable of reporting how much of what is being used. Most can compile that information into some form of statistical report. Reviewing that data allows for a rational assessment of how much capacity is being used and how much is still available. It also allows a knowledgeable person to make projections of how much more sharing is possible with what level of impact. Request that information and, if necessary, get help in interpreting it. Then you can make a cost-benefit decision based on fact. |