Welcome to www.minisinbox.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.

Copyright music expiration For Many Copyright Music Expiration is a Luxury for Worry If you copyright music, expiration isn't something you have to worry about, at least not in your lifetime. The music that you've written is copyrighted the moment you've put it onto paper or recorded it being played. The reason you don't have to worry about expiration is because the music is protected until 70 years after the death of the author. In the case of your music, that author would be you. This rule about copyright music expiration was first put into place so that the families and heirs of an author could still earn royalties even after his or her death. Ultimately this means that if you've taken the steps to copyright your music and have registered the copyright then your music will be protected throughout your lifetime until 70 years after you or the last surviving author (assuming a collaboration) are no longer living. Copyright music expiration is not something you should make a primary concern unless you are having issues of someone respecting and/or honoring your copyright at the moment. You should take comfort in the fact that as long as you are alive you are the only one who can assign your copyright to another person and as long as you haven't given up your ownership of the music it still belongs to you. This is different however if your copyrighted music was work made for hire. If that is the case then you cannot have ownership of the music, as it never legally belonged to you no matter what form it was in when it changed hands. Works made for hire have different copyright music expiration than those that were owned by the creator. With works made for hire, the copyrights are in effect for 95 years from the original publication date or for 120 years from the creation of the work whichever of the two is shorter. For most beginning musician’s copyright music expiration date isn't as important as getting that first gig or earning that first dollar as a result of the music he or she writes and/or plays. It's about art for many and about survival for others. The latter are quite often the ones that are taken advantage of. These are the authors who don't protect themselves as they should and end up failing to register their music because the idea of buying food seemed more pertinent to survival at the moment. This is often the case, particularly among street musicians and it's something that was becoming a growing problem immediately after hurricane Katrina devastated New Orleans taking with it many of the homes of starving musicians along with many pieces of music that will never become copyright music, expiration or not, those works are gone forever except in the mind of their creators. who could barely scrape together the money to pay $100 a month for a hovel they shared with 6 or 7 other people in order to keep expenses down and avoid living on the streets. The building not only of homes for those musicians displaced as a result of Katrina's devastation is wonderful but even more than that is the fact that there are organizations that are dedicated to creating a community for these musicians so that maybe many of the struggling artists won't be taken advantage of or have to face the decision to register their music in order to protect and copyright music expiration for their future heirs or to risk loosing their claim over the music they wrote in order to eat or pay the rent or buy groceries.

International Software Copyright International Software Agreement is a Matter of National Security Is there one governing law concerning international software copyright? According to agreements by the World Trade Organization (WTO) and the Trade-Related Aspects of Intellectual Property Rights (TRIP) any software written has an automatic copyright. This is a pretty conclusive consensus as far as an international copyright goes. The short answer would have been yes, but this was so much more informative. An international software copyright should not however be confused with a patent. Copyrights provide creators with the ability to prevent others from directly copying the code involved. A patent can actually limit the use of the software. Because of this, I'm sure you'll understand that patents are a hotly debated topic when it comes to software. The biggest thing to know about international software copyright is that your code is essentially protected the moment you create it. This is, unless you have some kind of contract through your employer that all code created by your belongs to them (these cases have been known to happen and provide excellent incentives for employees to always read the fine print). The problem that many companies are running into when it comes to enforcing international software copyright is that computers are not permanent fixtures in a company. Computers are rather disposable hardware when it comes to keeping up with evolving technologies and software needs to be updated when new computers are purchased. Rather than purchasing new copies of software when the computers are replaced companies are notorious for reusing old copies of the software. They are also famous for replacing 10 computers with the software installed with 40 new computers and installing the 10 copies of the software on all 40 computers. This is not in keeping with international software copyright. This is stealing and you'd be surprised at some of the good upstanding companies that do this on a regular basis. There really are no major differences between traditional policies for American copyright and international software copyright which makes legal issues, troubles, and woes that much easier to deal with. By having a unified international front thee are ramifications and legal actions that can be taken around the world without going through a great deal of international red tape. If you think dealing with the American government is bad, you should see how much fun it is to deal with the American government and another government for a legal action. The agreement between nations for international software copyright is probably one of the soundest possible decisions that can be made as military secrets of all governments have some degree of software in order to keep them operating. While it isn't quite as simplistic as stealing a computer program to unlock the defense secrets of a nation, having access to certain source codes could be problematic in the absolute best-case scenario. Keeping secrets isn't the only thing that makes this agreement so valuable, it is however, one of the most vital. Perhaps one of the greatest things to come about as the result of the international agreement to protect and honor software copyright is the peace of mind that is available to software developers in America and other technologically advanced countries that their source code won't be allowed to be stolen and used against them at a later date by someone in a developing nation with cheap labor and other overhead costs that American corporations simply cannot compete with. This could be devastating to the economies of technological societies if it were allowed to happen and the agreement for an international software copyright prevents that from being allowed to occur.